From: Chao Leng <lengchao@huawei.com>
To: <linux-nvme@lists.infradead.org>, <linux-block@vger.kernel.org>
Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de, lengchao@huawei.com,
sagi@grimberg.me
Subject: [PATCH v2 0/3] reduce quiesce time for lots of name spaces
Date: Fri, 7 Aug 2020 17:05:59 +0800 [thread overview]
Message-ID: <20200807090559.29582-1-lengchao@huawei.com> (raw)
nvme_stop_queues quiesce queues for all name spaces, now quiesce one by
one, if there is lots of name spaces, sync wait long time(more than 10s).
Multipath can not fail over to retry quickly, cause io pause long time.
This is not expected.
To reduce quiesce time, we introduce async mechanism for sync SRCUs
and quiesce queue.
Changes from v1:
- add support for blocking queue.
- introduce async mechanism for sync SRCU
- introduce async mechanism for quiesce queue
Chao Leng (3):
rcu: introduce async mechanism for sync SRCU
blk-mq: introduce async mechanism for quiesce queue
nvme-core: reduce io pause time when fail over
block/blk-mq.c | 28 ++++++++++++++++++++++++++++
drivers/nvme/host/core.c | 7 ++++++-
include/linux/blk-mq.h | 2 ++
include/linux/rcupdate_wait.h | 6 ++++++
include/linux/srcu.h | 1 +
include/linux/srcutiny.h | 2 ++
include/linux/srcutree.h | 2 ++
kernel/rcu/srcutiny.c | 15 +++++++++++++++
kernel/rcu/srcutree.c | 26 ++++++++++++++++++++++++++
kernel/rcu/update.c | 11 +++++++++++
10 files changed, 99 insertions(+), 1 deletion(-)
--
2.16.4
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-08-07 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 9:05 Chao Leng [this message]
2020-08-07 13:49 ` [PATCH v2 0/3] reduce quiesce time for lots of name spaces Ming Lei
2020-08-07 16:37 ` Sagi Grimberg
2020-08-10 2:17 ` Chao Leng
2020-08-10 3:15 ` Ming Lei
2020-08-11 3:13 ` Chao Leng
2020-08-11 20:53 ` Sagi Grimberg
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=20200807090559.29582-1-lengchao@huawei.com \
--to=lengchao@huawei.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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).