From: ming.lei@redhat.com (Ming Lei)
Subject: [PATCH 0/3] blk-mq: allow to unfreeze queue when io isn't drained
Date: Tue, 18 Sep 2018 18:13:07 +0800 [thread overview]
Message-ID: <20180918101310.13154-1-ming.lei@redhat.com> (raw)
Hi,
The 1st patch introduces percpu_ref_resurge() for implementing
blk_mq_unfreeze_queue_no_drain_io().
The 2nd patch introdces blk_mq_unfreeze_queue_no_drain_io() for
cases in which queue can be unfreeze without draininig IO.
The 3rd patch applies blk_mq_unfreeze_queue_no_drain_io() to
NVMe PCI timeout, so that IO hang may be avoided inside
nvme_reset_work() when new IO timeout is triggered.
Part of idea is from Jianchao's early work:
https://marc.info/?l=linux-kernel&m=153612052611020&w=2
Ming Lei (3):
lib/percpu-refcount: introduce percpu_ref_resurge()
blk-mq: introduce blk_mq_unfreeze_queue_no_drain_io
nvme: don't drain IO in nvme_reset_work()
block/blk-mq.c | 25 ++++++++++++++--
drivers/nvme/host/core.c | 12 +++++---
drivers/nvme/host/nvme.h | 2 +-
drivers/nvme/host/pci.c | 3 +-
include/linux/blk-mq.h | 1 +
include/linux/percpu-refcount.h | 1 +
lib/percpu-refcount.c | 63 ++++++++++++++++++++++++++++++++++-------
7 files changed, 87 insertions(+), 20 deletions(-)
Cc: Tejun Heo <tj at kernel.org>
Cc: Jianchao Wang <jianchao.w.wang at oracle.com>
Cc: Kent Overstreet <kent.overstreet at gmail.com>
Cc: linux-block at vger.kernel.org
Cc: Christoph Hellwig <hch at lst.de>
Cc: linux-nvme at lists.infradead.org
Cc: Keith Busch <keith.busch at intel.com>
--
2.9.5
next reply other threads:[~2018-09-18 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 10:13 Ming Lei [this message]
2018-09-18 10:13 ` [PATCH 2/3] blk-mq: introduce blk_mq_unfreeze_queue_no_drain_io Ming Lei
2018-09-18 10:13 ` [PATCH 3/3] nvme: don't drain IO in nvme_reset_work() Ming Lei
2018-09-18 10:16 ` [PATCH 0/3] blk-mq: allow to unfreeze queue when io isn't drained 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=20180918101310.13154-1-ming.lei@redhat.com \
--to=ming.lei@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;
as well as URLs for NNTP newsgroup(s).