From: Nilay Shroff <nilay@linux.ibm.com>
To: Qiliang Yuan <odys.yuan@gmail.com>, Jens Axboe <axboe@kernel.dk>,
Hannes Reinecke <hare@suse.de>, Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] block: don't quiesce the queue when setting the default elevator
Date: Mon, 12 Oct 2026 13:56:14 +0530 [thread overview]
Message-ID: <0c3a6b07-b6ca-4ef2-abcd-6b4e5a5c3fbe@linux.ibm.com> (raw)
In-Reply-To: <20261001-bug-block-elevator-init-quiesce-v1-1-5c85fa0ec59b@gmail.com>
On 10/1/26 8:40 AM, Qiliang Yuan wrote:
> elevator_set_default() runs from blk_register_queue() while the disk is
> still being added: the block device is not visible yet and uevents are
> suppressed, so no file system I/O can be issued. elevator_change()
> freezes the queue and cancels the dispatch work before switching, which
> is enough to drain dispatch activity from passthrough requests, as the
> comment in elevator_change() already states.
>
> elevator_switch() still quiesces the queue unconditionally, though, so
> every disk added with a default elevator waits for an RCU grace period.
> Commit 245a489e81e1 ("block: avoid to quiesce queue in
> elevator_init_mq") had removed this wait from the default elevator
> setup, and it came back when that setup was folded into
> elevator_change().
>
> The wait is paid in full by callers that add disks one at a time. ublk
> adds the disk of a single-queue device from START_DEV, which takes 7.7ms
> at p50 in a 16 vCPU KVM guest, most of it in blk_mq_quiesce_queue()
> called from elevator_set_default().
>
> Skip quiescing in elevator_switch() when setting the default elevator.
>
> ublk null target, 1000 single-queue devices created one by one:
>
> before after
> START_DEV p50 7.74ms 0.68ms
> START_DEV p99 14.61ms 1.32ms
> devices/s 114 971
>
> Fixes: 1e44bedbc921 ("block: unifying elevator change")
> Cc:stable@vger.kernel.org
> Signed-off-by: Qiliang Yuan<odys.yuan@gmail.com>
> ---
> block/elevator.c | 7 +++++--
> block/elevator.h | 2 ++
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/block/elevator.c b/block/elevator.c
> index 2161b6eea680c..da9ba70ac9321 100644
> --- a/block/elevator.c
> +++ b/block/elevator.c
> @@ -573,7 +573,8 @@ static int elevator_switch(struct request_queue *q, struct elv_change_ctx *ctx)
> return -EINVAL;
> }
>
> - blk_mq_quiesce_queue(q);
> + if (!ctx->no_quiesce)
> + blk_mq_quiesce_queue(q);
>
> if (q->elevator) {
> ctx->old = q->elevator;
> @@ -594,7 +595,8 @@ static int elevator_switch(struct request_queue *q, struct elv_change_ctx *ctx)
> blk_add_trace_msg(q, "elv switch: %s", ctx->name);
>
> out_unfreeze:
> - blk_mq_unquiesce_queue(q);
> + if (!ctx->no_quiesce)
> + blk_mq_unquiesce_queue(q);
>
One minor nit: Since we only unquiesce the queue at the out_unfreeze label,
could you rename it to out_unquiesce while you're at it? I realize this label
predates your change, but the new name would better reflect what happens there.
Otherwise, this change looks good to me.
Reviewed-by: Nilay Shroff <nilay@linux.ibm.com>
prev parent reply other threads:[~2026-10-12 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 3:10 Qiliang Yuan
2026-10-10 2:36 ` Qiliang Yuan
2026-10-10 3:17 ` Qiliang Yuan
2026-10-10 4:18 ` Ming Lei
2026-10-12 8:26 ` Nilay Shroff [this message]
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=0c3a6b07-b6ca-4ef2-abcd-6b4e5a5c3fbe@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=odys.yuan@gmail.com \
--cc=stable@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
all inboxes | Powered by JetHome®