linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 0/8] NVMe controller shutdown related patches
Date: Wed, 20 Feb 2013 17:19:28 -0700	[thread overview]
Message-ID: <1361405968-22085-1-git-send-email-keith.busch@intel.com> (raw)

These are all related to shutting down a controller for various reasons. We do
not want to take the gendisks down so that IO may continue. The nvme queues,
though, have to be deleted so the bio queueing had change so that it is not
queued on the nvme IO queues but on the device itself, which is what patch
[1/8] tries to do. 

The original motivation was to handle if the controller is in a temporary
failed state that a controller reset would clear up.

Another thread on the nvme mailing list pointed out potential issues that could
happen with the current IO timeout error handling should the controller end up
completing an IO the driver canceled internally, so it was adapted to address
that.

Resetting the controller for these situations is much the same as the
suspend/resume power management scenarios, and for a user controlled controller
reset for firmware activate, so more patches were added for these as well.

Keith Busch (8):
  NVMe: Queue bio requests on device
  NVMe: Controller reset from user
  NVMe: Suspend/resume power management
  NVMe: Add shutdown callback
  NVMe: End queued bio requests for removed disks
  NVMe: Wait for controller status ready to clear
  NVMe: Automatically reset failed controller
  NVMe: Use schedule_timeout for sync commands

 drivers/block/nvme.c |  313 ++++++++++++++++++++++++++++++++++++++++++--------
 1 files changed, 264 insertions(+), 49 deletions(-)

                 reply	other threads:[~2013-02-21  0:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1361405968-22085-1-git-send-email-keith.busch@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).