From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v1 2/3] nvme: Use blk-mq helper for IO termination
Date: Tue, 2 Feb 2016 16:49:15 +0000 [thread overview]
Message-ID: <20160202164915.GB10728@localhost.localdomain> (raw)
In-Reply-To: <BJXPR01MB1992E35D667BC3289F424CAE0DF0@BJXPR01MB199.CHNPR01.prod.partner.outlook.cn>
On Tue, Feb 02, 2016@04:32:33PM +0000, Wenbo Wang wrote:
> If some requests are in q->request_list or ctx->rq_list, does nvme_cancel_io remove them from these lists? If not, will it cause any issue?
It's fine to let them queue there if we expect to restart the
controller. We're going to restart the queues shortly.
If we're about to kill the queue, blk-mq's timeout handler kills
unstarted requests.
next prev parent reply other threads:[~2016-02-02 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 12:44 [PATCH RESEND v1 0/3] Move active IO termination to the core Sagi Grimberg
2016-02-02 12:44 ` [PATCH v1 1/3] blk-mq: Export tagset iter function Sagi Grimberg
2016-02-02 12:44 ` [PATCH v1 2/3] nvme: Use blk-mq helper for IO termination Sagi Grimberg
2016-02-02 16:32 ` Wenbo Wang
2016-02-02 16:49 ` Keith Busch [this message]
2016-02-03 0:35 ` Wenbo Wang
2016-02-03 1:26 ` Keith Busch
2016-02-04 14:28 ` Wenbo Wang
2016-02-04 15:44 ` Keith Busch
2016-02-05 6:53 ` Wenbo Wang
2016-02-02 12:44 ` [PATCH v1 3/3] blk-mq: Make blk_mq_all_tag_busy_iter static Sagi Grimberg
2016-02-10 10:12 ` [PATCH RESEND v1 0/3] Move active IO termination to the core Sagi Grimberg
2016-03-09 14:32 ` Christoph Hellwig
2016-03-09 15:57 ` Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2016-01-10 8:59 [PATCH " Sagi Grimberg
2016-01-10 8:59 ` [PATCH v1 2/3] nvme: Use blk-mq helper for IO termination Sagi Grimberg
2016-01-15 16:48 ` Keith Busch
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=20160202164915.GB10728@localhost.localdomain \
--to=keith.busch@intel.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