From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH 06/11] block: optimize generic_make_request for direct to blk-mq issue
Date: Sun, 26 Apr 2020 10:53:52 +0800 [thread overview]
Message-ID: <20200426025352.GA512559@T590> (raw)
In-Reply-To: <20200425170944.968861-7-hch@lst.de>
On Sat, Apr 25, 2020 at 07:09:39PM +0200, Christoph Hellwig wrote:
> Don't bother with the on-stack bio list if we know that we directly
> issue to a request based driver that can't re-inject bios.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-core.c | 29 +++++++++++++++++++----------
> 1 file changed, 19 insertions(+), 10 deletions(-)
>
> diff --git a/block/blk-core.c b/block/blk-core.c
> index 732d5b8d3cd25..e8c48203b2c55 100644
> --- a/block/blk-core.c
> +++ b/block/blk-core.c
> @@ -1008,6 +1008,18 @@ generic_make_request_checks(struct bio *bio)
> return false;
> }
>
> +static inline blk_qc_t __direct_make_request(struct bio *bio)
> +{
> + struct request_queue *q = bio->bi_disk->queue;
> + blk_qc_t ret;
> +
> + if (unlikely(bio_queue_enter(bio)))
> + return BLK_QC_T_NONE;
> + ret = blk_mq_make_request(q, bio);
> + blk_queue_exit(q);
> + return ret;
> +}
> +
> static blk_qc_t do_make_request(struct bio *bio,
> struct bio_list bio_list_on_stack[2])
> {
> @@ -1116,7 +1128,10 @@ blk_qc_t generic_make_request(struct bio *bio)
> return BLK_QC_T_NONE;
> }
>
> - return __generic_make_request(bio);
> + if (bio->bi_disk->queue->make_request_fn)
> + return __generic_make_request(bio);
> + return __direct_make_request(bio);
> +
blk_mq_make_request() still calls into generic_make_request(), so bio
may be added to current->bio_list, then looks __direct_make_request()
can't cover recursive bio submission any more.
Thanks,
Ming
next prev parent reply other threads:[~2020-04-26 2:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 17:09 [RFC] more make_request optimizations Christoph Hellwig
2020-04-25 17:09 ` [PATCH 01/11] block: improve the kerneldoc comments for submit_bio and generic_make_request Christoph Hellwig
2020-04-26 2:59 ` Ming Lei
2020-04-25 17:09 ` [PATCH 02/11] block: cleanup the memory stall accounting in submit_bio Christoph Hellwig
2020-04-25 17:09 ` [PATCH 03/11] block: replace BIO_QUEUE_ENTERED with BIO_CGROUP_ACCT Christoph Hellwig
2020-04-25 17:09 ` [PATCH 04/11] block: add a bio_queue_enter helper Christoph Hellwig
2020-04-25 17:09 ` [PATCH 05/11] block: refactor generic_make_request Christoph Hellwig
2020-04-25 17:09 ` [PATCH 06/11] block: optimize generic_make_request for direct to blk-mq issue Christoph Hellwig
2020-04-26 2:53 ` Ming Lei [this message]
2020-04-27 15:10 ` Christoph Hellwig
2020-04-25 17:09 ` [PATCH 07/11] block: optimize do_make_request " Christoph Hellwig
2020-04-25 17:09 ` [PATCH 08/11] block: move the call to blk_queue_enter_live out of blk_mq_get_request Christoph Hellwig
2020-04-25 17:09 ` [PATCH 09/11] block: remove a pointless queue enter pair in blk_mq_alloc_request Christoph Hellwig
2020-04-25 17:09 ` [PATCH 10/11] block: remove a pointless queue enter pair in blk_mq_alloc_request_hctx Christoph Hellwig
2020-04-25 17:09 ` [PATCH 11/11] block: allow blk_mq_make_request to consume the q_usage_counter reference Christoph Hellwig
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=20200426025352.GA512559@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.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).