From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>,
ming.lei@redhat.com, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: avoid blk_bio_segment_split for small I/O operations
Date: Mon, 4 Nov 2019 11:24:25 -0700 [thread overview]
Message-ID: <22bacf28-c17f-91c8-e30b-ccdc367b1c21@kernel.dk> (raw)
In-Reply-To: <20191104180543.23123-1-hch@lst.de>
On 11/4/19 11:05 AM, Christoph Hellwig wrote:
> __blk_queue_split() adds significant overhead for small I/O operations.
> Add a shortcut to avoid it for cases where we know we never need to
> split.
>
> Based on a patch from Ming Lei.
Applied, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2019-11-04 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 18:05 [PATCH] block: avoid blk_bio_segment_split for small I/O operations Christoph Hellwig
2019-11-04 18:24 ` Jens Axboe [this message]
2019-11-04 19:30 ` Keith Busch
2019-11-04 20:13 ` Jens Axboe
2019-11-04 22:50 ` Keith Busch
2019-11-04 22:55 ` Jens Axboe
2019-11-04 22:57 ` Christoph Hellwig
2019-11-04 22:59 ` Jens Axboe
2019-11-04 22:58 ` Bart Van Assche
2019-11-04 23:04 ` Keith Busch
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=22bacf28-c17f-91c8-e30b-ccdc367b1c21@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--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 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).