From: Hannes Reinecke <hare@suse.de>
To: Ming Lei <tom.leiming@gmail.com>, Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Cc: Yi Zhang <yizhan@redhat.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v1 3/3] blk-mq: start to freeze queue just after setting dying
Date: Sat, 18 Mar 2017 12:27:33 +0100 [thread overview]
Message-ID: <790d13bd-987a-cfde-deba-b874062d1e0b@suse.de> (raw)
In-Reply-To: <20170317095711.5819-4-tom.leiming@gmail.com>
On 03/17/2017 10:57 AM, Ming Lei wrote:
> Before commit 780db2071a(blk-mq: decouble blk-mq freezing
> from generic bypassing), the dying flag is checked before
> entering queue, and Tejun converts the checking into .mq_freeze_depth,
> and assumes the counter is increased just after dying flag
> is set. Unfortunately we doesn't do that in blk_set_queue_dying().
>
> This patch calls blk_mq_freeze_queue_start() for blk-mq in
> blk_set_queue_dying(), so that we can block new I/O coming
> once the queue is set as dying.
>
> Given blk_set_queue_dying() is always called in remove path
> of block device, and queue will be cleaned up later, we don't
> need to worry about undoing the counter.
>
> Cc: Bart Van Assche <bart.vanassche@sandisk.com>
> Cc: Tejun Heo <tj@kernel.org>
> Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> ---
> block/blk-core.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
prev parent reply other threads:[~2017-03-18 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 9:57 [PATCH v1 0/3] blk-mq: dying queue fix & improvement Ming Lei
2017-03-17 9:57 ` [PATCH v1 1/3] blk-mq: don't complete un-started request in timeout handler Ming Lei
2017-03-18 11:24 ` Hannes Reinecke
2017-03-17 9:57 ` [PATCH v1 2/3] blk-mq: comment on races related with " Ming Lei
2017-03-17 17:39 ` Bart Van Assche
2017-03-17 18:23 ` Ming Lei
2017-03-18 11:25 ` Hannes Reinecke
2017-03-17 9:57 ` [PATCH v1 3/3] blk-mq: start to freeze queue just after setting dying Ming Lei
2017-03-17 17:32 ` Bart Van Assche
2017-03-17 18:32 ` Ming Lei
2017-03-17 20:36 ` Bart Van Assche
2017-03-17 23:26 ` Bart Van Assche
2017-03-18 1:01 ` Ming Lei
2017-03-18 11:27 ` Hannes Reinecke [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=790d13bd-987a-cfde-deba-b874062d1e0b@suse.de \
--to=hare@suse.de \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=tom.leiming@gmail.com \
--cc=yizhan@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
all inboxes | Powered by JetHome®