Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1512984
| From | Ming Lei <tom.leiming@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 15/60] block: loop: comment on direct access to bvec table |
| Date | 2016-11-01 00:10 +0100 |
| Message-ID | <sytSi-uI-11@gated-at.bofh.it> (permalink) |
| References | <sxx1U-3GR-3@gated-at.bofh.it> <sxx1U-3GR-13@gated-at.bofh.it> <symQN-4eD-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Oct 31, 2016 at 11:31 PM, Christoph Hellwig <hch@infradead.org> wrote: > Btw, the lib/iov_iter.c code that iterates over bvec currently > expects single-page segments. Is the loop code fine with that? lib/iov_iter.c has switched to bvec iterator already in the mp-bvec preparing patchset, so every thing will be fine after multipage bvec is enabled. Another multipage bvec benefit for lib/iov_iter.c(dio) is that we can return whole pages in one segment, instead of one page each time, such as iov_iter_get_pages(), but that can be a follow-up optimization. > Even if it is I think we'd be much better off if it becomes multipage > segment aware. This patch is for auditing possible effect with multipage bvec, so looks we should expose as much as possible direct access to bvec table. Thanks, Ming Lei
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 15/60] block: loop: comment on direct access to bvec table Ming Lei <tom.leiming@gmail.com> - 2016-10-29 10:20 +0200
Re: [PATCH 15/60] block: loop: comment on direct access to bvec table Christoph Hellwig <hch@infradead.org> - 2016-10-31 16:40 +0100
Re: [PATCH 15/60] block: loop: comment on direct access to bvec table Ming Lei <tom.leiming@gmail.com> - 2016-11-01 00:10 +0100
csiph-web