linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swise@opengridcomputing.com (Steve Wise)
Subject: Reconnect on RDMA device reset
Date: Tue, 30 Jan 2018 11:51:12 -0600	[thread overview]
Message-ID: <038501d399f2$eb2740f0$c175c2d0$@opengridcomputing.com> (raw)
In-Reply-To: <1517333096.27592.281.camel@redhat.com>

> 
> In my original email, I pointed out that I didn't know how the NVMe over
> Fabrics was doing addressing.  If it were like SRP, then it wouldn't
> work because the device GUID is part of the addressing scheme, so a new
> device wouldn't automatically show as matching that address.  If,
> however, you use IP like iSER, then yes, I agree fully you can just test
> the ability to route over the new device using the IP address and
> restore if it works.

NVME-oF/rdma uses the rdma_cm with ip addresses, ip ports, etc...

      reply	other threads:[~2018-01-30 17:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 15:07 Reconnect on RDMA device reset Oren Duer
2018-01-23 12:42 ` Sagi Grimberg
2018-01-24  7:41   ` Oren Duer
2018-01-24 20:52     ` Sagi Grimberg
2018-01-25 14:10       ` Oren Duer
2018-01-29 19:58         ` Sagi Grimberg
2018-01-25 18:13       ` Doug Ledford
2018-01-25 19:06         ` Chuck Lever
2018-01-29 20:01           ` Sagi Grimberg
2018-01-29 20:11             ` Chuck Lever
2018-01-29 21:27               ` Doug Ledford
2018-01-29 21:46                 ` Chuck Lever
2018-01-25 22:48         ` Jason Gunthorpe
2018-01-29 20:36         ` Sagi Grimberg
2018-01-29 21:34           ` Bart Van Assche
2018-01-29 22:28           ` Doug Ledford
2018-01-30 15:03             ` Oren Duer
2018-01-30 17:24               ` Doug Ledford
2018-01-30 17:51                 ` Steve Wise [this message]

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='038501d399f2$eb2740f0$c175c2d0$@opengridcomputing.com' \
    --to=swise@opengridcomputing.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).