From: Damien Le Moal <dlemoal@kernel.org>
To: Yu Kuai <yukuai1@huaweicloud.com>,
ming.lei@redhat.com, yukuai3@huawei.com, tj@kernel.org,
josef@toxicpanda.com, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, johnny.chenyi@huawei.com
Subject: Re: [PATCH RFC v2 5/5] blk-mq-sched: support request batch dispatching for sq elevator
Date: Mon, 16 Jun 2025 12:07:47 +0900 [thread overview]
Message-ID: <9002cafb-4517-43be-9949-e09101a453ba@kernel.org> (raw)
In-Reply-To: <20250614092528.2352680-6-yukuai1@huaweicloud.com>
On 6/14/25 18:25, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
>
> Before this patch, each context will hold a global lock to dispatch one
> request at a time, which introduce intense lock competition:
How so ? If there is only a single context issuing IOs, there will not be any
contention on the lock.
> lock
> ops.dispatch_request
> unlock
>
> Hence support dispatch a batch of requests while holding the lock to
> reduce lock contention.
Lock contention would happen only if you have multiple processes issuing I/Os.
For a single context case, this simply reduces the overhead of dispatching
commands by avoiding the lock+unlock per request. So please explain that clearly.
>
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
> ---
> block/blk-mq-sched.c | 55 ++++++++++++++++++++++++++++++++++++++++----
> block/blk-mq.h | 21 +++++++++++++++++
> 2 files changed, 72 insertions(+), 4 deletions(-)
>
> diff --git a/block/blk-mq-sched.c b/block/blk-mq-sched.c
> index 990d0f19594a..d7cb88c8e8c7 100644
> --- a/block/blk-mq-sched.c
> +++ b/block/blk-mq-sched.c
> @@ -101,6 +101,49 @@ static bool elevator_can_dispatch(struct sched_dispatch_ctx *ctx)
> return true;
> }
>
> +static void elevator_dispatch_requests(struct sched_dispatch_ctx *ctx)
> +{
> + struct request *rq;
> + int budget_token[BUDGET_TOKEN_BATCH];
> + int count;
> + int i;
These 2 can be declared on the same line.
> +
> + while (true) {
> + if (!elevator_can_dispatch(ctx))
> + return;
> +
> + count = blk_mq_get_dispatch_budgets(ctx->q, budget_token);
> + if (count <= 0)
> + return;
> +
> + elevator_lock(ctx->e);
> + for (i = 0; i < count; ++i) {
> + rq = ctx->e->type->ops.dispatch_request(ctx->hctx);
> + if (!rq) {
> + ctx->run_queue = true;
> + goto err_free_budgets;
> + }
> +
> + blk_mq_set_rq_budget_token(rq, budget_token[i]);
> + list_add_tail(&rq->queuelist, &ctx->rq_list);
> + ctx->count++;
> + if (rq->mq_hctx != ctx->hctx)
> + ctx->multi_hctxs = true;
> +
> + if (!blk_mq_get_driver_tag(rq)) {
> + i++;
> + goto err_free_budgets;
> + }
> + }
> + elevator_unlock(ctx->e);
> + }
> +
> +err_free_budgets:
> + elevator_unlock(ctx->e);
> + for (; i < count; ++i)> + blk_mq_put_dispatch_budget(ctx->q, budget_token[i]);
> +}
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-06-16 3:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 9:25 [PATCH RFC v2 0/5] blk-mq-sched: support request batch dispatching for sq elevator Yu Kuai
2025-06-14 9:25 ` [PATCH RFC v2 1/5] elevator: introduce global lock for sq_shared elevator Yu Kuai
2025-06-16 2:38 ` Damien Le Moal
2025-06-14 9:25 ` [PATCH RFC v2 2/5] mq-deadline: switch to use elevator lock Yu Kuai
2025-06-16 2:41 ` Damien Le Moal
2025-06-14 9:25 ` [PATCH RFC v2 3/5] block, bfq: " Yu Kuai
2025-06-16 2:46 ` Damien Le Moal
2025-06-14 9:25 ` [PATCH RFC v2 4/5] blk-mq-sched: refactor __blk_mq_do_dispatch_sched() Yu Kuai
2025-06-16 2:54 ` Damien Le Moal
2025-06-14 9:25 ` [PATCH RFC v2 5/5] blk-mq-sched: support request batch dispatching for sq elevator Yu Kuai
2025-06-16 3:07 ` Damien Le Moal [this message]
2025-06-16 4:03 ` [PATCH RFC v2 0/5] " Damien Le Moal
2025-06-16 7:22 ` Yu Kuai
2025-06-16 7:37 ` Damien Le Moal
2025-06-16 9:14 ` Yu Kuai
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=9002cafb-4517-43be-9949-e09101a453ba@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=johnny.chenyi@huawei.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=tj@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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.