From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Atchley, Scott" <atchleyes@ornl.gov>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux RDMA Mailing List <linux-rdma@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] Remote access to pmem on storage targets
Date: Tue, 26 Jan 2016 09:00:21 -0800 [thread overview]
Message-ID: <20160126170021.GA21672@infradead.org> (raw)
In-Reply-To: <D0C5C0B9-A1A2-4428-B3CA-7BBCC5BEF10D@oracle.com>
On Tue, Jan 26, 2016 at 10:29:35AM -0500, Chuck Lever wrote:
> As I understand it, NVMf devices look like local devices.
> NVMf devices need globally unique naming to enable safe use
> with pNFS and other remote storage access protocols.
NVMe provides global uniqueue identifiers similar to SCSI, and in fact
there is even a standardised mapping to SCSI. The current SCSI layout
draft will work fine with both multi ported PCIe NVMe devices as well
as future fabrics devices.
next prev parent reply other threads:[~2016-01-26 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 21:19 [LSF/MM TOPIC] Remote access to pmem on storage targets Chuck Lever
2016-01-26 8:25 ` [Lsf-pc] " Jan Kara
2016-01-26 15:58 ` Chuck Lever
2016-01-27 0:04 ` Dave Chinner
2016-01-27 15:55 ` Chuck Lever
2016-01-28 21:10 ` Dave Chinner
2016-01-27 10:52 ` Sagi Grimberg
2016-01-26 15:25 ` Atchley, Scott
2016-01-26 15:29 ` Chuck Lever
2016-01-26 17:00 ` Christoph Hellwig [this message]
2016-01-27 16:54 ` [LSF/MM TOPIC/ATTEND] RDMA passive target Boaz Harrosh
2016-01-27 17:02 ` [Lsf-pc] " James Bottomley
2016-01-27 17:27 ` Sagi Grimberg
2016-01-31 14:20 ` Boaz Harrosh
2016-01-31 16:55 ` Yigal Korman
2016-02-01 10:36 ` 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=20160126170021.GA21672@infradead.org \
--to=hch@infradead.org \
--cc=atchleyes@ornl.gov \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).