linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: linux-nvme@lists.infradead.org
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
	Daniel Wagner <dwagner@suse.de>, Hannes Reinecke <hare@suse.de>
Subject: [PATCH rfc 0/6] support traddr as dns names for ip based transports
Date: Mon, 24 Jul 2023 12:20:16 +0300	[thread overview]
Message-ID: <20230724092023.708335-1-sagi@grimberg.me> (raw)

Currently nvme-cli is able to resolve an ip address from a dns name if
traddr argument was given as a dns name, so it does that and passes down
to the kernel the resolved ip address.

However, if the dns resolution changes over time, the kernel will not
be able to reconnect because it has a stale ip address. While this is
not a real use case for nvme subsystems, it could be a valid use-case
for discovery controllers, where the resolution is made from a dns
name that may load-balance/failover over multiple endpoints.

The last patch (7/6) is for libnvme to pass down the traddr as a dns
name if the kernel supports dns queries.

The inspiration was taken from the nfs client that does this for
redirects or locations discovery.

It is an rfc, so feedback is welcome.

Sagi Grimberg (6):
  nvme-fabrics: add helper to resolve ipv4/ipv6 or dns name
  nvme-tcp: use nvmf_resolve_address helper
  nvme-tcp: re-resolve traddr upon reconnect in case it is a dns name
  nvme-rdma: use nvmf_resolve_address helper
  nvme-rdma: re-resolve traddr upon reconnect in case it is a dns name
  nvme-fabrics: expose support for traddr as dns names to userspace

 drivers/nvme/host/fabrics.c | 29 +++++++++++++++++++++++++++++
 drivers/nvme/host/fabrics.h |  2 ++
 drivers/nvme/host/rdma.c    | 21 +++++++++++++--------
 drivers/nvme/host/tcp.c     | 21 +++++++++++++--------
 4 files changed, 57 insertions(+), 16 deletions(-)

-- 
2.41.0



             reply	other threads:[~2023-07-24  9:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  9:20 Sagi Grimberg [this message]
2023-07-24  9:20 ` [PATCH rfc 1/6] nvme-fabrics: add helper to resolve ipv4/ipv6 or dns name Sagi Grimberg
2023-08-10 13:29   ` Hannes Reinecke
2023-08-13 12:54     ` Sagi Grimberg
2023-07-24  9:20 ` [PATCH rfc 2/6] nvme-tcp: use nvmf_resolve_address helper Sagi Grimberg
2023-08-10 13:30   ` Hannes Reinecke
2023-08-13 12:55     ` Sagi Grimberg
2023-07-24  9:20 ` [PATCH rfc 3/6] nvme-tcp: re-resolve traddr upon reconnect in case it is a dns name Sagi Grimberg
2023-08-10 13:30   ` Hannes Reinecke
2023-07-24  9:20 ` [PATCH rfc 4/6] nvme-rdma: use nvmf_resolve_address helper Sagi Grimberg
2023-08-10 13:31   ` Hannes Reinecke
2023-07-24  9:20 ` [PATCH rfc 5/6] nvme-rdma: re-resolve traddr upon reconnect in case it is a dns name Sagi Grimberg
2023-08-10 13:31   ` Hannes Reinecke
2023-07-24  9:20 ` [PATCH rfc 6/6] nvme-fabrics: expose support for traddr as dns names to userspace Sagi Grimberg
2023-08-10 13:33   ` Hannes Reinecke
2023-08-13 13:07     ` Sagi Grimberg
2023-08-17  9:11       ` Sagi Grimberg
2023-08-17  9:41         ` Hannes Reinecke
2023-08-17 10:37           ` Sagi Grimberg
2023-08-17 10:48             ` Hannes Reinecke
2023-08-17 11:09               ` Sagi Grimberg
2023-08-17 14:39                 ` Daniel Wagner
2023-08-20 10:55                   ` Sagi Grimberg
2023-08-21  6:08                     ` Daniel Wagner
2023-08-21  7:44                       ` Sagi Grimberg
2023-07-24  9:20 ` [PATCH rfc libnvme 7/6] fabrics: pass traddr dns name if the kernel supports it Sagi Grimberg
2023-08-10 12:03 ` [PATCH rfc 0/6] support traddr as dns names for ip based transports Sagi Grimberg
2023-08-10 12:33   ` Daniel Wagner
2023-08-10 13:24   ` Hannes Reinecke
2023-08-10 13:29   ` Belanger, Martin
2023-08-10 13:30     ` Belanger, Martin
2023-08-10 13:34 ` Hannes Reinecke
2023-08-13 13:09   ` Sagi Grimberg

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=20230724092023.708335-1-sagi@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=dwagner@suse.de \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.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).