From: sim@linux.vnet.ibm.com (Narasimhan V)
Subject: nguid for nvme over fabrics
Date: Fri, 30 Mar 2018 22:16:51 +0530 [thread overview]
Message-ID: <a4f728e9ce2ca0905c641614d1330a1f@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180328082708.GA31409@infradead.org>
On 2018-03-28 13:57, Christoph Hellwig wrote:
> 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.
Thnaks Chris,
I get it now.
>
> Which means that you generally should not set a nguid unless you
> are building an appliance and really know what you are doing.
>
For my confirmation, if we are setting duplicate nguids, it is user's
responsibility, and system does not give any warning / error ?
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
--
Regards
Narasimhan V
prev parent reply other threads:[~2018-03-30 16:46 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
2018-03-30 16:46 ` Narasimhan V [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=a4f728e9ce2ca0905c641614d1330a1f@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