From: Ming Lei <ming.lei@redhat.com>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] iov_iter: optimise iov_iter_npages for bvec
Date: Fri, 20 Nov 2020 10:22:00 +0800 [thread overview]
Message-ID: <20201120022200.GB333150@T590> (raw)
In-Reply-To: <35d5db17-f6f6-ec32-944e-5ecddcbcb0f1@gmail.com>
On Fri, Nov 20, 2020 at 01:39:05AM +0000, Pavel Begunkov wrote:
> On 20/11/2020 01:20, Matthew Wilcox wrote:
> > On Thu, Nov 19, 2020 at 11:24:38PM +0000, Pavel Begunkov wrote:
> >> The block layer spends quite a while in iov_iter_npages(), but for the
> >> bvec case the number of pages is already known and stored in
> >> iter->nr_segs, so it can be returned immediately as an optimisation
> >
> > Er ... no, it doesn't. nr_segs is the number of bvecs. Each bvec can
> > store up to 4GB of contiguous physical memory.
>
> Ah, really, missed min() with PAGE_SIZE in bvec_iter_len(), then it's a
> stupid statement. Thanks!
>
iov_iter_npages(bvec) still can be improved a bit by the following way:
diff --git a/lib/iov_iter.c b/lib/iov_iter.c
index 1635111c5bd2..d85ed7acce05 100644
--- a/lib/iov_iter.c
+++ b/lib/iov_iter.c
@@ -1608,17 +1608,23 @@ int iov_iter_npages(const struct iov_iter *i, int maxpages)
npages = pipe_space_for_user(iter_head, pipe->tail, pipe);
if (npages >= maxpages)
return maxpages;
+ } else if (iov_iter_is_bvec(i)) {
+ unsigned idx, offset = i->iov_offset;
+
+ for (idx = 0; idx < i->nr_segs; idx++) {
+ npages += DIV_ROUND_UP(i->bvec[idx].bv_len - offset,
+ PAGE_SIZE);
+ offset = 0;
+ }
+ if (npages >= maxpages)
+ return maxpages;
} else iterate_all_kinds(i, size, v, ({
unsigned long p = (unsigned long)v.iov_base;
npages += DIV_ROUND_UP(p + v.iov_len, PAGE_SIZE)
- p / PAGE_SIZE;
if (npages >= maxpages)
return maxpages;
- 0;}),({
- npages++;
- if (npages >= maxpages)
- return maxpages;
- }),({
+ 0;}),0,({
unsigned long p = (unsigned long)v.iov_base;
npages += DIV_ROUND_UP(p + v.iov_len, PAGE_SIZE)
- p / PAGE_SIZE;
--
Ming
next prev parent reply other threads:[~2020-11-20 2:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 23:24 [PATCH v2 0/2] optimise iov_iter Pavel Begunkov
2020-11-19 23:24 ` [PATCH v2 1/2] iov_iter: optimise iov_iter_npages for bvec Pavel Begunkov
2020-11-20 1:20 ` Matthew Wilcox
2020-11-20 1:39 ` Pavel Begunkov
2020-11-20 1:49 ` Matthew Wilcox
2020-11-20 1:56 ` Pavel Begunkov
2020-11-20 2:06 ` Matthew Wilcox
2020-11-20 2:08 ` Pavel Begunkov
2020-11-20 2:24 ` Ming Lei
2020-11-20 17:22 ` Pavel Begunkov
2020-11-20 17:23 ` Pavel Begunkov
2020-11-20 2:22 ` Ming Lei [this message]
2020-11-20 2:25 ` Pavel Begunkov
2020-11-20 2:54 ` Matthew Wilcox
2020-11-20 8:14 ` Christoph Hellwig
2020-11-20 12:39 ` Matthew Wilcox
2020-11-20 13:00 ` Pavel Begunkov
2020-11-20 13:13 ` Matthew Wilcox
2020-11-20 9:57 ` Pavel Begunkov
2020-11-20 13:29 ` David Laight
2020-11-19 23:24 ` [PATCH v2 2/2] iov_iter: optimise iter type checking Pavel Begunkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201120022200.GB333150@T590 \
--to=ming.lei@redhat.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).