From: Sagi Grimberg <sagi@grimberg.me>
To: Daniel Wagner <dwagner@suse.de>
Cc: Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Subject: Re: [PATCH rfc 6/6] nvme-fabrics: expose support for traddr as dns names to userspace
Date: Mon, 21 Aug 2023 10:44:02 +0300 [thread overview]
Message-ID: <1e56aa0a-d957-f31e-eef9-a143a7ac4bd5@grimberg.me> (raw)
In-Reply-To: <vzcluo7jktlrut4iavcdyrsdedcg4cpsm72ewuqwrq2sjqkce3@ik3imkps3llf>
> The libnvme parser is ignore anything it doesn't know yet. Introducing
> 'feat' or 'cap' is not a problem at all. Also it should be fairly simple
> to add. The resulting code is likely to be very similar too; testing if
> feat/cap or dns_ip_addr token is available and then use the dns name.
>
> Given this, I am in favor of the feat/cap approach.
I do still want to hear others. We have thumbs up from Daniel and
Hannes.
next prev parent reply other threads:[~2023-08-21 7:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 9:20 [PATCH rfc 0/6] support traddr as dns names for ip based transports Sagi Grimberg
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 [this message]
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=1e56aa0a-d957-f31e-eef9-a143a7ac4bd5@grimberg.me \
--to=sagi@grimberg.me \
--cc=chaitanya.kulkarni@wdc.com \
--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).