From: hch@infradead.org (Christoph Hellwig)
Subject: nguid for nvme over fabrics
Date: Wed, 28 Mar 2018 01:27:08 -0700 [thread overview]
Message-ID: <20180328082708.GA31409@infradead.org> (raw)
In-Reply-To: <0832b33613cb166a1c3f46dd3c5d407d@linux.vnet.ibm.com>
On Fri, Mar 23, 2018@12:59:53PM +0530, Narasimhan V wrote:
> Shouldn't it be unique ?
> I have instances where for NVMef, multiple devices can have same nguids.
> Which component should be responsible to generate nguid in NVMef ?
You must only usea nguid if you have a ieee id, and then it is your
responsibility to hand out ids based on that.
Which means that you generally should not set a nguid unless you
are building an appliance and really know what you are doing.
next prev parent reply other threads:[~2018-03-28 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 8:59 nguid for nvme over fabrics Narasimhan V
2018-03-22 19:02 ` Sagi Grimberg
2018-03-23 7:29 ` Narasimhan V
2018-03-28 8:27 ` Christoph Hellwig [this message]
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=20180328082708.GA31409@infradead.org \
--to=hch@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