From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, Zhang Yi <yizhan@redhat.com>,
linux-block@vger.kernel.org,
Johannes Thumshirn <jthumshirn@suse.de>,
Ming Lei <ming.lei@redhat.com>
Subject: [PATCH v2 0/3] nvme: fix hang in path of removing disk
Date: Sat, 20 May 2017 11:56:02 +0800 [thread overview]
Message-ID: <20170520035605.21785-1-ming.lei@redhat.com> (raw)
The first two patches fixes hang during removing disk.
The 3rd patch removes blk_mq_abort_requeue_list() since
no one uses it any more.
Ming Lei (3):
nvme: use blk_mq_start_hw_queues() in nvme_kill_queues()
nvme: avoid to use blk_mq_abort_requeue_list()
blk-mq: remove blk_mq_abort_requeue_list()
block/blk-mq.c | 19 -------------------
drivers/nvme/host/core.c | 13 ++++++++++---
include/linux/blk-mq.h | 1 -
3 files changed, 10 insertions(+), 23 deletions(-)
--
2.9.4
WARNING: multiple messages have this Message-ID (diff)
From: ming.lei@redhat.com (Ming Lei)
Subject: [PATCH v2 0/3] nvme: fix hang in path of removing disk
Date: Sat, 20 May 2017 11:56:02 +0800 [thread overview]
Message-ID: <20170520035605.21785-1-ming.lei@redhat.com> (raw)
The first two patches fixes hang during removing disk.
The 3rd patch removes blk_mq_abort_requeue_list() since
no one uses it any more.
Ming Lei (3):
nvme: use blk_mq_start_hw_queues() in nvme_kill_queues()
nvme: avoid to use blk_mq_abort_requeue_list()
blk-mq: remove blk_mq_abort_requeue_list()
block/blk-mq.c | 19 -------------------
drivers/nvme/host/core.c | 13 ++++++++++---
include/linux/blk-mq.h | 1 -
3 files changed, 10 insertions(+), 23 deletions(-)
--
2.9.4
next reply other threads:[~2017-05-20 3:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 3:56 Ming Lei [this message]
2017-05-20 3:56 ` [PATCH v2 0/3] nvme: fix hang in path of removing disk Ming Lei
2017-05-20 3:56 ` [PATCH v2 1/3] nvme: use blk_mq_start_hw_queues() in nvme_kill_queues() Ming Lei
2017-05-20 3:56 ` Ming Lei
2017-05-21 6:20 ` Christoph Hellwig
2017-05-21 6:20 ` Christoph Hellwig
2017-05-22 1:35 ` Ming Lei
2017-05-22 1:35 ` Ming Lei
2017-05-22 12:51 ` Christoph Hellwig
2017-05-22 12:51 ` Christoph Hellwig
2017-05-22 14:49 ` Ming Lei
2017-05-22 14:49 ` Ming Lei
2017-05-22 5:35 ` Keith Busch
2017-05-22 5:35 ` Keith Busch
2017-05-22 7:41 ` Johannes Thumshirn
2017-05-22 7:41 ` Johannes Thumshirn
2017-05-20 3:56 ` [PATCH v2 2/3] nvme: avoid to use blk_mq_abort_requeue_list() Ming Lei
2017-05-20 3:56 ` Ming Lei
2017-05-20 5:34 ` Ming Lei
2017-05-20 5:34 ` Ming Lei
2017-05-21 6:22 ` Christoph Hellwig
2017-05-21 6:22 ` Christoph Hellwig
2017-05-22 7:42 ` Johannes Thumshirn
2017-05-22 7:42 ` Johannes Thumshirn
2017-05-22 5:35 ` Keith Busch
2017-05-22 5:35 ` Keith Busch
2017-05-20 3:56 ` [PATCH v2 3/3] blk-mq: remove blk_mq_abort_requeue_list() Ming Lei
2017-05-20 3:56 ` Ming Lei
2017-05-21 6:22 ` Christoph Hellwig
2017-05-21 6:22 ` Christoph Hellwig
2017-05-22 5:36 ` Keith Busch
2017-05-22 5:36 ` Keith Busch
2017-05-22 7:43 ` Johannes Thumshirn
2017-05-22 7:43 ` Johannes Thumshirn
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=20170520035605.21785-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yizhan@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.