From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>,
linux-nvme@lists.infradead.org,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH V2 0/4] block: fix concurrent quiesce
Date: Tue, 09 Nov 2021 08:14:53 -0700 [thread overview]
Message-ID: <163647089353.413881.8401016435701752543.b4-ty@kernel.dk> (raw)
In-Reply-To: <20211109071144.181581-1-ming.lei@redhat.com>
On Tue, 9 Nov 2021 15:11:40 +0800, Ming Lei wrote:
> Convert SCSI into balanced quiesce and unquiesce by using atomic
> variable as suggested by James, meantime fix previous nvme conversion by
> adding one new API because we have to wait until the started quiesce is
> done.
>
> V2:
> - add comment on scsi's change, as suggested by James, 3/4
> - add reviewed-by tag, 4/4
>
> [...]
Applied, thanks!
[1/4] blk-mq: add one API for waiting until quiesce is done
commit: 9ef4d0209cbadb63656a7aa29fde49c27ab2b9bf
[2/4] scsi: avoid to quiesce sdev->request_queue two times
commit: d2b9f12b0f7cf95c43f5fd4a18688d958d39e423
[3/4] scsi: make sure that request queue queiesce and unquiesce balanced
commit: 93542fbfa7b726d053c01a9399577c03968c4f6b
[4/4] nvme: wait until quiesce is done
commit: 26af1cd00364ce20dbec66b93ef42f9d42dc6953
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2021-11-09 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 7:11 [PATCH V2 0/4] block: fix concurrent quiesce Ming Lei
2021-11-09 7:11 ` [PATCH V2 1/4] blk-mq: add one API for waiting until quiesce is done Ming Lei
2021-11-09 7:11 ` [PATCH V2 2/4] scsi: avoid to quiesce sdev->request_queue two times Ming Lei
2021-11-09 7:11 ` [PATCH V2 3/4] scsi: make sure that request queue queiesce and unquiesce balanced Ming Lei
2021-11-09 7:11 ` [PATCH V2 4/4] nvme: wait until quiesce is done Ming Lei
2021-11-09 14:41 ` [PATCH V2 0/4] block: fix concurrent quiesce Martin K. Petersen
2021-11-09 15:14 ` Jens Axboe [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=163647089353.413881.8401016435701752543.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=James.Bottomley@hansenpartnership.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.