linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] block: don't protect submit_bio_checks by q_usage_counter
Date: Mon, 10 Jan 2022 08:05:08 +0800	[thread overview]
Message-ID: <Ydt4NK82C3rx2EuW@T590> (raw)
In-Reply-To: <20220104134223.590803-1-ming.lei@redhat.com>

On Tue, Jan 04, 2022 at 09:42:23PM +0800, Ming Lei wrote:
> Commit cc9c884dd7f4 ("block: call submit_bio_checks under q_usage_counter")
> uses q_usage_counter to protect submit_bio_checks for avoiding IO after
> disk is deleted by del_gendisk().
> 
> Turns out the protection isn't necessary, because once
> blk_mq_freeze_queue_wait() in del_gendisk() returns:
> 
> 1) all in-flight IO has been done
> 
> 2) all new IO will be failed in __bio_queue_enter() because
>    q_usage_counter is dead, and GD_DEAD is set
> 
> 3) both disk and request queue instance are safe since caller of
> submit_bio() guarantees that the disk can't be closed.
> 
> Once submit_bio_checks() needn't the protection of q_usage_counter, we can
> move submit_bio_checks before calling blk_mq_submit_bio() and
> ->submit_bio(). With this change, we needn't to throttle queue with
> holding one allocated request, then precise driver tag or request won't be
> wasted in throttling. Meantime we can unify the bio check for both bio
> based and request based driver.
> 
> Cc: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>

Hello,

Any comments on this fix?

-- 
Ming


  reply	other threads:[~2022-01-10  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 13:42 [PATCH] block: don't protect submit_bio_checks by q_usage_counter Ming Lei
2022-01-10  0:05 ` Ming Lei [this message]
2022-01-10  1:56 ` Jens Axboe
2022-01-10  1:59 ` Jens Axboe
2022-01-10 16:49 ` Christoph Hellwig
2022-01-11  1:16   ` 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=Ydt4NK82C3rx2EuW@T590 \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).