All of lore.kernel.org
 help / color / mirror / Atom feed
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: [RFC 0/2] optimise split bio
Date: Tue,  5 Jan 2021 19:43:36 +0000	[thread overview]
Message-ID: <cover.1609875589.git.asml.silence@gmail.com> (raw)

With the no-copy bvec patches and nullb eats blk_bio_segment_split()
eats >7%. It adds yet another fast path for it.

        8K              16K             32K             64K
before: 932             904             868             788
after:  934             919             902             862

Would appreciate if anyone knows off the bat typical queue_max_segments, etc.
numbers for NVMe.

Pavel Begunkov (2):
  block: add a function for *segment_split fast path
  block: add a fast path for seg split of large bio

 block/blk-merge.c | 107 +++++++++++++++++++++++++++++-----------------
 1 file changed, 68 insertions(+), 39 deletions(-)

-- 
2.24.0


             reply	other threads:[~2021-01-05 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 19:43 Pavel Begunkov [this message]
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
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=cover.1609875589.git.asml.silence@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.