linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: Q: nvme_rdma and reconnect
Date: Wed, 21 Dec 2016 22:41:15 -0800	[thread overview]
Message-ID: <20161222064115.GA9581@infradead.org> (raw)
In-Reply-To: <830460a5-ce31-b882-8f06-4a906763eb50@broadcom.com>

On Wed, Dec 21, 2016@04:56:41PM -0800, James Smart wrote:
> Sagi, Christoph,
> 
> Can you explain what the difference is between the "reset" path and the
> "error/reconnect" path is in the rdma driver.  From my point of view, it
> would seem both, relative to the fabric-side of the transport, are
> terminating the controller and reconnecting to a new controller to recover.
> So why wouldn't they be the same (single) reset flow ?

They should use the same flow.  A couple month ago I had a prototype
for that but never got it to work fully.

  parent reply	other threads:[~2016-12-22  6:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 18:39 [PATCH] nvmet: fix KATO offset in Set Features Daniel Verkamp
2016-12-07 19:09 ` Daniel Verkamp
2016-12-09 18:28   ` Christoph Hellwig
2016-12-09 20:04     ` Daniel Verkamp
2016-12-21 10:27       ` Christoph Hellwig
     [not found]         ` <830460a5-ce31-b882-8f06-4a906763eb50@broadcom.com>
2016-12-22  6:41           ` Christoph Hellwig [this message]
2016-12-22 12:08             ` Q: nvme_rdma and reconnect Sagi Grimberg
2016-12-22 12:10               ` Christoph Hellwig
2016-12-22 12:52                 ` Sagi Grimberg
2016-12-22 12:46               ` Hannes Reinecke
2016-12-22 12:50                 ` Christoph Hellwig
2016-12-09 19:59 ` [PATCH v2] nvmet: fix KATO offset in Set Features Daniel Verkamp

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=20161222064115.GA9581@infradead.org \
    --to=hch@infradead.org \
    /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).