From: Christoph Hellwig <hch@lst.de>
To: John Meneghini <jmeneghi@redhat.com>
Cc: Israel Rukshin <israelr@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Linux-nvme <linux-nvme@lists.infradead.org>,
Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Ewan Milne <emilne@redhat.com>, Tomas Bzatek <tbzatek@redhat.com>,
"Farley, Douglas" <Douglas.Farley@dell.com>,
"Ballard, Curtis C (HPE Storage)" <curtis.ballard@hpe.com>,
Frederick Knight <Frederick.Knight@kioxia.com>,
James Smart <james.smart@broadcom.com>
Subject: Re: [PATCH V2] fabrics: Always pass hostid and hostnqn
Date: Fri, 19 Apr 2024 07:14:52 +0200 [thread overview]
Message-ID: <20240419051452.GA11501@lst.de> (raw)
In-Reply-To: <04c77907-073a-4adf-8a6a-a2b3af28a853@redhat.com>
On Thu, Apr 18, 2024 at 05:48:41PM -0400, John Meneghini wrote:
> The first is TP-4110 Align Fabrics and PCIe Host Identifier Setting.
>
> From TP-4110: this is requirement for the controller.
Only if you actually implement the TP. I don't see any reason why
we should implement it.
> Basically, we want to allow all Fabric hosts to connect with HostID == 0.
No, we don't. Some people who pushed the agenda in the working group
did and we had to fight to not make it even worse than what got
released. Doing so would be a retrograde step.
> There is also TP-4126 NVMe-oF Boot HostNQN and HostID. This is a requirement for the host.
No, it is not. It is a way to be helpful if people implemet the braindead
pre-boot stuff. There is no real need to do that.
prev parent reply other threads:[~2024-04-19 5:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 14:24 [PATCH V2] fabrics: Always pass hostid and hostnqn Israel Rukshin
2024-04-18 14:24 ` [PATCH V2] libnvme: Introduce functions to generate host identifier and host NQN Israel Rukshin
2024-05-22 12:54 ` Daniel Wagner
2024-04-18 21:48 ` [PATCH V2] fabrics: Always pass hostid and hostnqn John Meneghini
2024-04-19 5:14 ` Christoph Hellwig [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=20240419051452.GA11501@lst.de \
--to=hch@lst.de \
--cc=Douglas.Farley@dell.com \
--cc=Frederick.Knight@kioxia.com \
--cc=curtis.ballard@hpe.com \
--cc=emilne@redhat.com \
--cc=israelr@nvidia.com \
--cc=james.smart@broadcom.com \
--cc=jmeneghi@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.com \
--cc=sagi@grimberg.me \
--cc=tbzatek@redhat.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