From: Ming Lei <ming.lei@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH REPOST] blk-mq: Don't disable preemption around __blk_mq_run_hw_queue().
Date: Tue, 21 Jun 2022 15:56:41 +0800 [thread overview]
Message-ID: <YrF5uf4ZL7Oh7LVJ@T590> (raw)
In-Reply-To: <YrF1p2n0MxHQ3fcJ@linutronix.de>
On Tue, Jun 21, 2022 at 09:39:19AM +0200, Sebastian Andrzej Siewior wrote:
> __blk_mq_delay_run_hw_queue() disables preemption to get a stable
> current CPU number and then invokes __blk_mq_run_hw_queue() if the CPU
> number is part the mask.
>
> __blk_mq_run_hw_queue() acquires a spin_lock_t which is a sleeping lock
> on PREEMPT_RT and can't be acquired with disabled preemption.
>
> If it is important that the current CPU matches the requested CPU mask
> and that the context does not migrate to another CPU while
> __blk_mq_run_hw_queue() is invoked then it possible to achieve this by
> disabling migration and keeping the context preemptible.
>
> Disable only migration while testing the CPU mask and invoking
> __blk_mq_run_hw_queue().
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Link: https://lore.kernel.org/r/YnQHqx/5+54jd+U+@linutronix.de
> Link: https://lore.kernel.org/r/YqISXf6GAQeWqcR+@linutronix.de
> ---
> block/blk-mq.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -2083,14 +2083,14 @@ static void __blk_mq_delay_run_hw_queue(
> return;
>
> if (!async && !(hctx->flags & BLK_MQ_F_BLOCKING)) {
> - int cpu = get_cpu();
> - if (cpumask_test_cpu(cpu, hctx->cpumask)) {
> + migrate_disable();
> + if (cpumask_test_cpu(raw_smp_processor_id(), hctx->cpumask)) {
> __blk_mq_run_hw_queue(hctx);
> - put_cpu();
> + migrate_enable();
I think you can replace it with raw_smp_processor_id() directly without
disabling migration.
Both async run queue and direct issue can run on cpu not on hctx->cpumask,
so it is fine for sync run queue too.
Thanks,
Ming
next prev parent reply other threads:[~2022-06-21 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 7:39 [PATCH REPOST] blk-mq: Don't disable preemption around __blk_mq_run_hw_queue() Sebastian Andrzej Siewior
2022-06-21 7:56 ` Ming Lei [this message]
2022-06-22 8:25 ` [PATCH v2] " Sebastian Andrzej Siewior
2022-06-22 8:35 ` Ming Lei
2022-06-22 17:46 ` Jens Axboe
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=YrF5uf4ZL7Oh7LVJ@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=tglx@linutronix.de \
/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