From: sim@linux.vnet.ibm.com (Narasimhan V)
Subject: nguid for nvme over fabrics
Date: Tue, 20 Mar 2018 14:29:43 +0530 [thread overview]
Message-ID: <410a2655c6f5e4ed9e1c2af36b72f3ee@linux.vnet.ibm.com> (raw)
Hi,
I am trying nvme over fabrics, and found this: nguid is set to 0s by
default for all devices.
So, nguid can be same (0s in this case) for multiple devices. Is this
valid ?
Also, same nguid for multiple devices could be set, by the above
scenario.
No errors/warnings from either the nvme initiator/target.
From spec, I see this:
Namespace Globally Unique Identifier (NGUID): This field contains a
128-bit value that is
globally unique and assigned to the namespace when the namespace
is created. This field
remains fixed throughout the life of the namespace and is preserved
across namespace and
controller operations (e.g., controller reset, namespace format, etc.).
--
Regards
Narasimhan V
next reply other threads:[~2018-03-20 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 8:59 Narasimhan V [this message]
2018-03-22 19:02 ` nguid for nvme over fabrics Sagi Grimberg
2018-03-23 7:29 ` Narasimhan V
2018-03-28 8:27 ` Christoph Hellwig
2018-03-30 16:46 ` Narasimhan V
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=410a2655c6f5e4ed9e1c2af36b72f3ee@linux.vnet.ibm.com \
--to=sim@linux.vnet.ibm.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