From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.de>,
Chao Leng <lengchao@huawei.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH V4 0/4] blk-mq: implement queue quiesce via percpu_ref for BLK_MQ_F_BLOCKING
Date: Wed, 9 Sep 2020 18:41:12 +0800 [thread overview]
Message-ID: <20200909104116.1674592-1-ming.lei@redhat.com> (raw)
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.
V4:
- remove .mq_quiesce_mutex, and switch to test_and_[set|clear] for
avoiding duplicated quiesce action
- pass blktests(block, nvme)
V3:
- add tagset quiesce interface
- apply tagset quiesce interface for NVMe
- pass blktests(block, nvme)
V2:
- add .mq_quiesce_lock
- add comment on patch 2 wrt. handling hctx_lock() failure
- trivial patch style change
Ming Lei (3):
block: use test_and_{clear|test}_bit to set/clear QUEUE_FLAG_QUIESCED
blk-mq: implement queue quiesce via percpu_ref for BLK_MQ_F_BLOCKING
blk-mq: add tagset quiesce interface
Sagi Grimberg (1):
nvme: use blk_mq_[un]quiesce_tagset
block/blk-core.c | 13 +++
block/blk-mq-sysfs.c | 2 -
block/blk-mq.c | 173 +++++++++++++++++++++++++--------------
block/blk-sysfs.c | 6 +-
block/blk.h | 2 +
drivers/nvme/host/core.c | 19 ++---
include/linux/blk-mq.h | 10 +--
include/linux/blkdev.h | 4 +
8 files changed, 146 insertions(+), 83 deletions(-)
Cc: Hannes Reinecke <hare@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>
Cc: Bart Van Assche <bvanassche@acm.org>
Cc: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Chao Leng <lengchao@huawei.com>
--
2.25.2
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-09-09 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 10:41 Ming Lei [this message]
2020-09-09 10:41 ` [PATCH V4 1/4] block: use test_and_{clear|test}_bit to set/clear QUEUE_FLAG_QUIESCED Ming Lei
2020-09-09 10:41 ` [PATCH V4 2/4] blk-mq: implement queue quiesce via percpu_ref for BLK_MQ_F_BLOCKING Ming Lei
2020-09-09 16:04 ` Keith Busch
2020-09-09 20:53 ` Sagi Grimberg
2020-09-10 8:03 ` Ming Lei
2020-09-10 1:53 ` Ming Lei
2020-09-10 14:55 ` Keith Busch
2020-09-09 10:41 ` [PATCH V4 3/4] blk-mq: add tagset quiesce interface Ming Lei
2020-09-09 10:41 ` [PATCH V4 4/4] nvme: use blk_mq_[un]quiesce_tagset 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=20200909104116.1674592-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--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=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).