linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v3 1/5] nvme core: allow controller RESETTING to RECONNECTING transition
Date: Tue, 17 Oct 2017 16:32:44 -0700	[thread overview]
Message-ID: <20171017233248.6769-2-jsmart2021@gmail.com> (raw)
In-Reply-To: <20171017233248.6769-1-jsmart2021@gmail.com>

Allow controller state transition : RESETTING to RECONNECTING

Transport will typically transition from LIVE->RESETTING when
initially performing a reset or recovering from an error. Adding
this transition allows a transport to transition to RECONNECTING
when it checks/waits for connectivity then creates new transport
connections and reinits the controller.

-- james

Signed-off-by: James Smart <james.smart at broadcom.com>
Reviewed-by: Christoph Hellwig <hch at lst.de>
Reviewed-by: Sagi Grimberg <sagi at grimberg.me>

---
v3: no change. incorporated Reviewed-by's
---
 drivers/nvme/host/core.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 26c8913435b2..aa9e2df27bf7 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -205,6 +205,7 @@ bool nvme_change_ctrl_state(struct nvme_ctrl *ctrl,
 	case NVME_CTRL_RECONNECTING:
 		switch (old_state) {
 		case NVME_CTRL_LIVE:
+		case NVME_CTRL_RESETTING:
 			changed = true;
 			/* FALLTHRU */
 		default:
-- 
2.13.1

  reply	other threads:[~2017-10-17 23:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 23:32 [PATCH v3 0/5] nvme_fc: add dev_loss_tmo support James Smart
2017-10-17 23:32 ` James Smart [this message]
2017-10-18  8:26   ` [PATCH v3 1/5] nvme core: allow controller RESETTING to RECONNECTING transition Johannes Thumshirn
2017-10-20  5:58   ` Hannes Reinecke
2017-10-17 23:32 ` [PATCH v3 2/5] nvme_fc: change ctlr state assignments during reset/reconnect James Smart
2017-10-18  8:27   ` Johannes Thumshirn
2017-10-20  6:00   ` Hannes Reinecke
2017-10-17 23:32 ` [PATCH v3 3/5] nvme_fc: add a dev_loss_tmo field to the remoteport James Smart
2017-10-18  8:28   ` Johannes Thumshirn
2017-10-20  6:04   ` Hannes Reinecke
2017-10-20 14:50     ` James Smart
2017-10-17 23:32 ` [PATCH v3 4/5] nvme_fc: check connectivity before initiating reconnects James Smart
2017-10-18  8:29   ` Johannes Thumshirn
2017-10-20  6:05   ` Hannes Reinecke
2017-10-17 23:32 ` [PATCH v3 5/5] nvme_fc: add dev_loss_tmo timeout and remoteport resume support James Smart
2017-10-19 15:46   ` Trapp, Darren
2017-10-19 18:04     ` James Smart
2017-10-19 19:49       ` Trapp, Darren
2017-10-20  6:27   ` Hannes Reinecke
2017-10-20 18:53     ` James Smart

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=20171017233248.6769-2-jsmart2021@gmail.com \
    --to=jsmart2021@gmail.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).