From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Ming Lei <ming.lei@redhat.com>, Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC 2/2] block: add a fast path for seg split of large bio
Date: Tue, 5 Jan 2021 20:36:34 +0000 [thread overview]
Message-ID: <32e083c2-2bd8-aafd-c5ed-5b41fd59eaca@gmail.com> (raw)
In-Reply-To: <53b86d4e86c4913658cb0f472dcc3e22ef75396b.1609875589.git.asml.silence@gmail.com>
On 05/01/2021 19:43, Pavel Begunkov wrote:
> blk_bio_segment_split() is very heavy, but the current fast path covers
> only one-segment under PAGE_SIZE bios. Add another one by estimating an
> upper bound of sectors a bio can contain.
>
> One restricting factor here is queue_max_segment_size(), which it
> compare against full iter size to not dig into bvecs. By default it's
> 64KB, and so for requests under 64KB, but for those falling under the
> conditions it's much faster.
>
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
> ---
> block/blk-merge.c | 29 +++++++++++++++++++++++++----
> 1 file changed, 25 insertions(+), 4 deletions(-)
>
[...]
>
> - return __blk_bio_segment_split(q, bio, bs, nr_segs);
> + q_max_sectors = get_max_io_size(q, bio);
> + if (!queue_virt_boundary(q) && bio_segs < queue_max_segments(q) &&
> + bio->bi_iter.bi_size <= queue_max_segment_size(q)) {
I think I miss a seg_boundary_mask check here. Any insights how to skip it?
Or why it's 2^31-1 by default, but not say ((unsigned long)-1)?
--
Pavel Begunkov
next prev parent reply other threads:[~2021-01-05 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 19:43 [RFC 0/2] optimise split bio Pavel Begunkov
2021-01-05 19:43 ` [RFC 1/2] block: add a function for *segment_split fast path Pavel Begunkov
2021-01-05 19:43 ` [RFC 2/2] block: add a fast path for seg split of large bio Pavel Begunkov
2021-01-05 20:36 ` Pavel Begunkov [this message]
2021-01-27 17:16 ` Christoph Hellwig
2021-01-28 11:56 ` Pavel Begunkov
2021-01-28 12:10 ` Ming Lei
2021-01-28 12:27 ` Pavel Begunkov
2021-01-29 2:00 ` Ming Lei
2021-02-01 10:59 ` 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=32e083c2-2bd8-aafd-c5ed-5b41fd59eaca@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.