public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, Yi Zhang <yi.zhang@redhat.com>,
	linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/4] scsi: make sure that request queue queiesce and unquiesce balanced
Date: Mon, 08 Nov 2021 22:22:46 -0500	[thread overview]
Message-ID: <33b8edaa46a755caceac183390bb6fa8a82315bd.camel@HansenPartnership.com> (raw)
In-Reply-To: <YYnooJNLvHIQA0Xk@T590>

On Tue, 2021-11-09 at 11:18 +0800, Ming Lei wrote:
> Hello James,
> 
> On Tue, Nov 09, 2021 at 08:44:06AM +0800, Ming Lei wrote:
> > Hello James,
> > 
> > On Mon, Nov 08, 2021 at 11:42:01AM -0500, James Bottomley wrote:
> > > On Wed, 2021-11-03 at 11:43 +0800, Ming Lei wrote:
> > > [...]
> > > > +void scsi_start_queue(struct scsi_device *sdev)
> > > > +{
> > > > +	if (cmpxchg(&sdev->queue_stopped, 1, 0))
> > > > +		blk_mq_unquiesce_queue(sdev->request_queue);
> > > > +}
> > > > +
> > > > +static void scsi_stop_queue(struct scsi_device *sdev, bool
> > > > nowait)
> > > > +{
> > > > +	if (!cmpxchg(&sdev->queue_stopped, 0, 1)) {
> > > > +		if (nowait)
> > > > +			blk_mq_quiesce_queue_nowait(sdev-
> > > > > request_queue);
> > > > +		else
> > > > +			blk_mq_quiesce_queue(sdev-
> > > > >request_queue);
> > > > +	} else {
> > > > +		if (!nowait)
> > > > +			blk_mq_wait_quiesce_done(sdev-
> > > > >request_queue);
> > > > +	}
> > > > +}
> > > 
> > > This looks counter intuitive.  I assume it's done so that if we
> > > call
> > > scsi_stop_queue when the queue has already been stopped, it waits
> > > until
> > 
> > The motivation is to balance
> > blk_mq_quiesce_queue_nowait()/blk_mq_quiesce_queue()
> > and blk_mq_unquiesce_queue().
> > 
> > That needs one extra mutex to cover the quiesce action and update
> > the flag, but we can't hold the mutex in
> > scsi_internal_device_block_nowait(),
> > so take this way with the atomic flag.
> > 
> > > the queue is actually quiesced before returning so the behaviour
> > > is the
> > > same in the !nowait case?  Some sort of comment explaining that
> > > would
> > > be useful.
> > 
> > I will add comment on the current usage.
> 
> Are you fine with the following comment?
> 
> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> index e8925a35cb3a..9e3bf028f95a 100644
> --- a/drivers/scsi/scsi_lib.c
> +++ b/drivers/scsi/scsi_lib.c
> @@ -2661,6 +2661,13 @@ void scsi_start_queue(struct scsi_device
> *sdev)
>  
>  static void scsi_stop_queue(struct scsi_device *sdev, bool nowait)
>  {
> +	/*
> +	 * The atomic variable of ->queue_stopped covers that
> +	 * blk_mq_quiesce_queue* is balanced with
> blk_mq_unquiesce_queue.
> +	 *
> +	 * However, we still need to wait until quiesce is done
> +	 * in case that queue has been stopped.
> +	 */
>  	if (!cmpxchg(&sdev->queue_stopped, 0, 1)) {
>  		if (nowait)
>  			blk_mq_quiesce_queue_nowait(sdev-
> >request_queue);

Yes, that looks fine ... it will at least act as a caution for
maintainers who come after us.

James



  reply	other threads:[~2021-11-09  3:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  3:43 [PATCH 0/4] block: fix concurrent quiesce Ming Lei
2021-11-03  3:43 ` [PATCH 1/4] blk-mq: add one API for waiting until quiesce is done Ming Lei
2021-11-03  3:43 ` [PATCH 2/4] scsi: avoid to quiesce sdev->request_queue two times Ming Lei
2021-11-03  3:43 ` [PATCH 3/4] scsi: make sure that request queue queiesce and unquiesce balanced Ming Lei
2021-11-08 16:42   ` James Bottomley
2021-11-09  0:44     ` Ming Lei
2021-11-09  3:18       ` Ming Lei
2021-11-09  3:22         ` James Bottomley [this message]
2021-11-03  3:43 ` [PATCH 4/4] nvme: wait until quiesce is done Ming Lei
2021-11-08 16:45   ` Keith Busch
2021-11-12 15:38   ` Sagi Grimberg
2021-11-07 21:20 ` [PATCH 0/4] block: fix concurrent quiesce 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=33b8edaa46a755caceac183390bb6fa8a82315bd.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    --cc=yi.zhang@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