From: Bart Van Assche <bvanassche@acm.org>
To: Jinlong Chen <nickyc975@zju.edu.cn>,
axboe@kernel.dk, kbusch@kernel.org, hch@lst.de, sagi@grimberg.me
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/3] blk-mq: remove redundant call to blk_freeze_queue_start in blk_mq_destroy_queue
Date: Sat, 29 Oct 2022 17:34:49 -0700 [thread overview]
Message-ID: <adaea16a-c7cd-5d68-50c8-d56de851061a@acm.org> (raw)
In-Reply-To: <ebd3a47a1ebf4ab518c985cdbaa1ac3afd6dfb9f.1667035519.git.nickyc975@zju.edu.cn>
On 10/29/22 03:02, Jinlong Chen wrote:
> Calling blk_freeze_queue results in a redundant call to
> blk_freeze_queue_start as it has been called in blk_queue_start_drain.
>
> Replace blk_freeze_queue with blk_mq_freeze_queue_wait to avoid the
> redundant call.
blk_mq_destroy_queue() has more callers than blk_queue_start_drain() so
the above description is at least misleading.
Additionally, the word "cleanup" from the patch series title indicates
that no patch in this series changes the behavior of the code. This
patch involves a behavior change.
I think this patch introduces a hang for every caller of
blk_mq_destroy_queue() other than blk_queue_start_drain().
Bart.
next prev parent reply other threads:[~2022-10-30 0:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 10:02 [PATCH 0/3] cleanups for queue freezing functions Jinlong Chen
2022-10-29 10:02 ` [PATCH 1/3] blk-mq: remove redundant call to blk_freeze_queue_start in blk_mq_destroy_queue Jinlong Chen
2022-10-30 0:34 ` Bart Van Assche [this message]
2022-10-30 2:27 ` Jinlong Chen
2022-10-30 14:25 ` Bart Van Assche
2022-10-30 14:55 ` Jinlong Chen
2022-10-30 20:19 ` Bart Van Assche
2022-10-31 2:02 ` Jinlong Chen
2022-10-29 10:02 ` [PATCH 2/3] blk-mq: remove blk_freeze_queue Jinlong Chen
2022-10-29 10:02 ` [PATCH 3/3] block: hide back blk_freeze_queue_start and export its blk-mq alias Jinlong Chen
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=adaea16a-c7cd-5d68-50c8-d56de851061a@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nickyc975@zju.edu.cn \
--cc=sagi@grimberg.me \
/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®