From: Mike Snitzer <snitzer@redhat.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org
Subject: Re: dm-rq: don't call blk_mq_queue_stopped in dm_stop_queue()
Date: Fri, 19 Jun 2020 05:42:50 -0400 [thread overview]
Message-ID: <20200619094250.GA18410@redhat.com> (raw)
In-Reply-To: <20200619084214.337449-1-ming.lei@redhat.com>
Hi Ming,
Thanks for the patch! But I'm having a hard time understanding what
you've written in the patch header,
On Fri, Jun 19 2020 at 4:42am -0400,
Ming Lei <ming.lei@redhat.com> wrote:
> dm-rq won't stop queue, meantime blk-mq won't stop one queue too, so
> remove the check.
It'd be helpful if you could unpack this with more detail before going on
to explain why using blk_queue_quiesced, despite dm-rq using
blk_mq_queue_stopped, would also be ineffective.
SO:
> dm-rq won't stop queue
1) why won't dm-rq stop the queue? Do you mean it won't reliably
_always_ stop the queue because of the blk_mq_queue_stopped() check?
> meantime blk-mq won't stop one queue too, so remove the check.
2) Meaning?: blk_mq_queue_stopped() will return true even if only one hw
queue is stopped, given blk-mq must stop all hw queues a positive return
from this blk_mq_queue_stopped() check is incorrectly assuming it meanss
all hw queues are stopped.
> dm_stop_queue() actually tries to quiesce hw queues via blk_mq_quiesce_queue(),
> we can't check via blk_queue_quiesced for avoiding unnecessary queue
> quiesce because the flag is set before synchronize_rcu() and dm_stop_queue
> may be called when synchronize_rcu from another blk_mq_quiesce_queue is
> in-progress.
But I'm left with questions/confusion on this too:
1) you mention blk_queue_quiesced instead of blk_mq_queue_stopped, so I
assume you mean that: not only is blk_mq_queue_stopped()
ineffective, blk_queue_quiesced() would be too?
2) the race you detail (with competing blk_mq_quiesce_queue) relative to
synchronize_rcu() and testing "the flag" is very detailed yet vague.
Anyway, once we get this heaader cleaned up a bit more I'll be happy to
get this staged as a stable@ fix for 5.8 inclusion ASAP.
Thanks!
Mike
>
> Cc: linux-block@vger.kernel.org
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> drivers/md/dm-rq.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/md/dm-rq.c b/drivers/md/dm-rq.c
> index f60c02512121..ed4d5ea66ccc 100644
> --- a/drivers/md/dm-rq.c
> +++ b/drivers/md/dm-rq.c
> @@ -70,9 +70,6 @@ void dm_start_queue(struct request_queue *q)
>
> void dm_stop_queue(struct request_queue *q)
> {
> - if (blk_mq_queue_stopped(q))
> - return;
> -
> blk_mq_quiesce_queue(q);
> }
>
> --
> 2.25.2
>
next prev parent reply other threads:[~2020-06-19 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 8:42 [PATCH] dm-rq: don't call blk_mq_queue_stopped in dm_stop_queue() Ming Lei
2020-06-19 9:42 ` Mike Snitzer [this message]
2020-06-19 10:11 ` Ming Lei
2020-06-19 16:06 ` Mike Snitzer
2020-06-19 17:40 ` Mike Snitzer
2020-06-19 22:37 ` Ming Lei
2020-06-19 22:52 ` Ming Lei
2020-06-19 23:04 ` Mike Snitzer
2020-06-19 23:14 ` Ming Lei
2020-06-19 23:37 ` Ming Lei
2020-06-19 22:23 ` 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=20200619094250.GA18410@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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;
as well as URLs for NNTP newsgroup(s).