Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: james.smart@broadcom.com (James Smart)
Subject: [PATCH 3/3] nvme: delete NVME_CTRL_LIVE --> NVME_CTRL_CONNECTING transition
Date: Wed, 31 Jan 2018 09:11:36 -0800	[thread overview]
Message-ID: <bb905705-7f96-a3e1-aa01-bd910a8a49fa@broadcom.com> (raw)
In-Reply-To: <1517416286-31109-4-git-send-email-maxg@mellanox.com>

On 1/31/2018 8:31 AM, Max Gurtovoy wrote:
> There is no logical reason to move from live state to connecting
> state. In case of initial connection establishment, the transition
> should be NVME_CTRL_NEW --> NVME_CTRL_CONNECTING --> NVME_CTRL_LIVE.
> In case of error recovery or reset, the transition should be
> NVME_CTRL_LIVE --> NVME_CTRL_RESETTING --> NVME_CTRL_CONNECTING -->
> NVME_CTRL_LIVE.
>
> Signed-off-by: Max Gurtovoy <maxg at mellanox.com>


Reviewed-by: James Smart <james.smart at broadcom.com>

  reply	other threads:[~2018-01-31 17:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 16:31 [PATCH v3 0/3] Fix host side state machine Max Gurtovoy
2018-01-31 16:31 ` [PATCH 1/3] nvme: rename NVME_CTRL_RECONNECTING state to NVME_CTRL_CONNECTING Max Gurtovoy
2018-01-31 17:10   ` James Smart
2018-02-08 15:28   ` Sagi Grimberg
2018-02-08 16:19     ` Sagi Grimberg
2018-02-13 10:19       ` Max Gurtovoy
2018-02-13 10:46         ` Sagi Grimberg
2018-02-13 18:01           ` Max Gurtovoy
2018-02-13 23:55           ` Max Gurtovoy
2018-02-14 13:40             ` Sagi Grimberg
2018-02-14 14:20               ` Max Gurtovoy
2018-02-15 18:09                 ` Max Gurtovoy
2018-01-31 16:31 ` [PATCH 2/3] nvme-rdma: use NVME_CTRL_CONNECTING state to mark init process Max Gurtovoy
2018-01-31 17:10   ` James Smart
2018-01-31 16:31 ` [PATCH 3/3] nvme: delete NVME_CTRL_LIVE --> NVME_CTRL_CONNECTING transition Max Gurtovoy
2018-01-31 17:11   ` James Smart [this message]
2018-02-05 14:46 ` [PATCH v3 0/3] Fix host side state machine Sagi Grimberg
2018-02-06 15:01   ` Max Gurtovoy
2018-02-08 16:01 ` 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=bb905705-7f96-a3e1-aa01-bd910a8a49fa@broadcom.com \
    --to=james.smart@broadcom.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