From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Oren Duer <oren.duer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Oren Duer <oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: Reconnect on RDMA device reset
Date: Tue, 30 Jan 2018 12:24:56 -0500 [thread overview]
Message-ID: <1517333096.27592.281.camel@redhat.com> (raw)
In-Reply-To: <CADZhsQpWXQQ2dKxAorGMhk7HFvqoQ2Y5LxVKt66XjkcUbEuXpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On Tue, 2018-01-30 at 17:03 +0200, Oren Duer wrote:
> Not sure why we need to keep track whether it is the same device or not.
> I fail to understand why we trust the system admin to create the connections
> at the beginning, but we should not trust him anymore if the device was
> removed, a new device was added in place of it, and it was configured with the
> same network IP/subnet. To me it looks like the admin wanted exactly that:
> for the connections to be restored over the new device.
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.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-30 17:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADZhsQqDFc1NWmsihOwki8_2Zj0HuYKC_N_x0jMnCtU9Rww1UA@mail.gmail.com>
[not found] ` <CADZhsQqDFc1NWmsihOwki8_2Zj0HuYKC_N_x0jMnCtU9Rww1UA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-23 12:42 ` Reconnect on RDMA device reset Sagi Grimberg
[not found] ` <f0a14240-1566-1bae-1b9f-21880bc3f3a0-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2018-01-24 7:41 ` Oren Duer
[not found] ` <CADZhsQqvK0LMd9sfxzz+x_5qVnoi4FP0FCFMsTPjpeXyqfXKew-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-24 20:52 ` Sagi Grimberg
[not found] ` <77cef33e-a563-97fc-7ba6-69f220f1be84-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2018-01-25 14:10 ` Oren Duer
[not found] ` <CADZhsQpM8=MXRU=_015f3bo_EisM8N4vL=8XkO1a4c4yHwbC3w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-29 19:58 ` Sagi Grimberg
2018-01-25 18:13 ` Doug Ledford
[not found] ` <1516904022.27592.187.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-25 19:06 ` Chuck Lever
[not found] ` <679C11A4-744C-4574-9F50-2D2C3B0F08B0-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2018-01-29 20:01 ` Sagi Grimberg
[not found] ` <92367a43-4c2e-887f-35ff-38fa05d47c49-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2018-01-29 20:11 ` Chuck Lever
[not found] ` <EFFF4091-3CBA-474B-B9D7-FF7EDA3B1613-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2018-01-29 21:27 ` Doug Ledford
[not found] ` <1517261240.27592.245.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-29 21:46 ` Chuck Lever
2018-01-25 22:48 ` Jason Gunthorpe
2018-01-29 20:36 ` Sagi Grimberg
[not found] ` <26056a83-2f81-6b56-7bbf-fcecfc4518d6-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2018-01-29 21:34 ` Bart Van Assche
2018-01-29 22:28 ` Doug Ledford
[not found] ` <1517264899.27592.277.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-30 15:03 ` Oren Duer
[not found] ` <CADZhsQpWXQQ2dKxAorGMhk7HFvqoQ2Y5LxVKt66XjkcUbEuXpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-30 17:24 ` Doug Ledford [this message]
[not found] ` <1517333096.27592.281.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-30 17:51 ` Steve Wise
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=1517333096.27592.281.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=oren.duer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.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