From: Jeff Moyer <jmoyer@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, Ming Lin <ming.l@ssi.samsung.com>,
Kent Overstreet <kent.overstreet@gmail.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 4/4] blk-mq: mark ctx as pending at batch in flush plug path
Date: Thu, 15 Oct 2015 11:26:43 -0400 [thread overview]
Message-ID: <x49lhb4gnkc.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1444793448-9994-5-git-send-email-ming.lei@canonical.com> (Ming Lei's message of "Wed, 14 Oct 2015 11:30:48 +0800")
Ming Lei <ming.lei@canonical.com> writes:
> Most of times, flush plug should be the hottest I/O path,
> so mark ctx as pending after all requests in the list are
> inserted.
Hi, Ming,
Did you see some performance gain from this?
-Jeff
>
> Signed-off-by: Ming Lei <ming.lei@canonical.com>
> ---
> block/blk-mq.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index deb5f4c..1c943b9 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -993,18 +993,25 @@ void blk_mq_delay_queue(struct blk_mq_hw_ctx *hctx, unsigned long msecs)
> }
> EXPORT_SYMBOL(blk_mq_delay_queue);
>
> -static void __blk_mq_insert_request(struct blk_mq_hw_ctx *hctx,
> - struct request *rq, bool at_head)
> +static inline void __blk_mq_insert_req_list(struct blk_mq_hw_ctx *hctx,
> + struct blk_mq_ctx *ctx,
> + struct request *rq,
> + bool at_head)
> {
> - struct blk_mq_ctx *ctx = rq->mq_ctx;
> -
> trace_block_rq_insert(hctx->queue, rq);
>
> if (at_head)
> list_add(&rq->queuelist, &ctx->rq_list);
> else
> list_add_tail(&rq->queuelist, &ctx->rq_list);
> +}
> +
> +static void __blk_mq_insert_request(struct blk_mq_hw_ctx *hctx,
> + struct request *rq, bool at_head)
> +{
> + struct blk_mq_ctx *ctx = rq->mq_ctx;
>
> + __blk_mq_insert_req_list(hctx, ctx, rq, at_head);
> blk_mq_hctx_mark_pending(hctx, ctx);
> }
>
> @@ -1060,8 +1067,9 @@ static void blk_mq_insert_requests(struct request_queue *q,
> rq = list_first_entry(list, struct request, queuelist);
> list_del_init(&rq->queuelist);
> rq->mq_ctx = ctx;
> - __blk_mq_insert_request(hctx, rq, false);
> + __blk_mq_insert_req_list(hctx, ctx, rq, false);
> }
> + blk_mq_hctx_mark_pending(hctx, ctx);
> spin_unlock(&ctx->lock);
>
> blk_mq_run_hw_queue(hctx, from_schedule);
next prev parent reply other threads:[~2015-10-15 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 3:30 [PATCH 0/4] block: some misc changes Ming Lei
2015-10-14 3:30 ` [PATCH 1/4] block: setup bi_phys_segments after splitting Ming Lei
2015-10-15 15:14 ` Jeff Moyer
2015-10-14 3:30 ` [PATCH 2/4] block: avoid to merge splitted bio Ming Lei
2015-10-15 15:15 ` Jeff Moyer
2015-10-14 3:30 ` [PATCH 3/4] blk-mq: check bio_mergeable() early before merging Ming Lei
2015-10-15 15:21 ` Jeff Moyer
2015-10-16 0:26 ` Ming Lei
2015-10-14 3:30 ` [PATCH 4/4] blk-mq: mark ctx as pending at batch in flush plug path Ming Lei
2015-10-15 15:26 ` Jeff Moyer [this message]
2015-10-16 0:24 ` Ming Lei
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=x49lhb4gnkc.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.l@ssi.samsung.com \
--cc=ming.lei@canonical.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
all inboxes | Powered by JetHome®