From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>
Cc: Hannes Reinecke <hare@suse.de>, Sagi Grimberg <sagi@grimberg.me>,
Bart Van Assche <bvanassche@acm.org>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Chao Leng <lengchao@huawei.com>
Subject: Re: [PATCH V5 0/4] blk-mq: implement queue quiesce via percpu_ref for BLK_MQ_F_BLOCKING
Date: Fri, 11 Sep 2020 12:05:28 -0600 [thread overview]
Message-ID: <8bb90a44-c088-9b10-8665-ec083063e49c@kernel.dk> (raw)
In-Reply-To: <20200911024117.62480-1-ming.lei@redhat.com>
On 9/10/20 8:41 PM, Ming Lei wrote:
> Hi Jens,
>
> The 1st patch add .mq_quiesce_mutex for serializing quiesce/unquiesce,
> and prepares for replacing srcu with percpu_ref.
>
> The 2nd patch replaces srcu with percpu_ref.
>
> The 3rd patch adds tagset quiesce interface.
>
> The 4th patch applies tagset quiesce interface for NVMe subsystem.
What is this series against?
--
Jens Axboe
next prev parent reply other threads:[~2020-09-11 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 2:41 [PATCH V5 0/4] blk-mq: implement queue quiesce via percpu_ref for BLK_MQ_F_BLOCKING Ming Lei
2020-09-11 2:41 ` [PATCH V5 1/4] block: use test_and_{clear|test}_bit to set/clear QUEUE_FLAG_QUIESCED Ming Lei
2020-09-11 6:03 ` Hannes Reinecke
2020-09-11 2:41 ` [PATCH V5 2/4] blk-mq: implement queue quiesce via percpu_ref for BLK_MQ_F_BLOCKING Ming Lei
2020-09-11 2:41 ` [PATCH V5 3/4] blk-mq: add tagset quiesce interface Ming Lei
2020-09-11 2:41 ` [PATCH V5 4/4] nvme: use blk_mq_[un]quiesce_tagset Ming Lei
2020-09-11 17:29 ` [PATCH V5 0/4] blk-mq: implement queue quiesce via percpu_ref for BLK_MQ_F_BLOCKING Sagi Grimberg
2020-09-11 18:34 ` Sagi Grimberg
2020-09-11 18:45 ` Jens Axboe
2020-09-11 23:28 ` Ming Lei
2020-09-11 17:33 ` Keith Busch
2020-09-11 18:05 ` Jens Axboe [this message]
2020-09-11 19:12 ` Sagi Grimberg
2020-09-11 19:14 ` Jens Axboe
2020-09-14 3:05 ` 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=8bb90a44-c088-9b10-8665-ec083063e49c@kernel.dk \
--to=axboe@kernel.dk \
--cc=Johannes.Thumshirn@wdc.com \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).