From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>,
Tim Walker <tim.t.walker@seagate.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: Re: Multi-Actuator SAS HDD First Look
Date: Mon, 9 Apr 2018 02:25:22 -0700 [thread overview]
Message-ID: <20180409092522.GA9394@infradead.org> (raw)
In-Reply-To: <361c204d-f9be-978a-5778-81ecaeb143e0@interlog.com>
On Fri, Apr 06, 2018 at 01:09:08PM -0400, Douglas Gilbert wrote:
> So you found a document that outlines NVMe's architecture! Could you
> share the url (no marketing BS, please)?
You can always take a look at the actual spec:
http://nvmexpress.org/wp-content/uploads/NVM-Express-1_3a-20171024_ratified.pdf
But in summary: while in SCSI your Nexus for any command is with the
logic unit, in NVMe it is with the controller. Many admin commands
operate on the whole controller.
> And a serious question ... How would you map NVMe's (in Linux)
> subsystem number, controller device minor number, CNTLID field
> (Identify ctl response) and namespace id onto the SCSI subsystem's
> h:c:t:l ?
I wouldn't because the scheme already doesn't make any sense for SCSI,
nevermind should we try to map NVMe into a scsi specific worldview.
>
> Doug Gilbert
>
---end quoted text---
prev parent reply other threads:[~2018-04-09 9:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 14:57 Multi-Actuator SAS HDD First Look Tim Walker
2018-03-26 15:08 ` Hannes Reinecke
2018-03-29 18:03 ` Douglas Gilbert
2018-03-30 13:07 ` Tim Walker
2018-03-30 18:07 ` Tim Walker
2018-03-30 18:17 ` Bart Van Assche
2018-03-30 18:21 ` Tim Walker
2018-03-30 18:31 ` Bart Van Assche
2018-03-30 18:36 ` Tim Walker
2018-03-30 20:01 ` Bart Van Assche
2018-03-31 16:52 ` Douglas Gilbert
2018-04-02 15:34 ` Tim Walker
2018-04-02 16:29 ` Douglas Gilbert
2018-04-02 16:44 ` Tim Walker
2018-03-31 12:21 ` Hannes Reinecke
2018-03-31 11:03 ` Hannes Reinecke
2018-04-03 7:46 ` Christoph Hellwig
2018-04-05 23:43 ` Tim Walker
2018-04-06 0:51 ` Douglas Gilbert
2018-04-06 6:24 ` Hannes Reinecke
2018-04-06 6:42 ` Christoph Hellwig
2018-04-06 17:09 ` Douglas Gilbert
2018-04-09 2:08 ` Tim Walker
2018-04-09 6:17 ` Hannes Reinecke
2018-04-09 16:02 ` Douglas Gilbert
2018-04-16 1:35 ` Tim Walker
2018-04-16 4:31 ` Bart Van Assche
2018-04-18 11:16 ` Tim Walker
2018-04-18 16:20 ` Bart Van Assche
2018-04-18 16:25 ` Tim Walker
2018-04-09 9:25 ` 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=20180409092522.GA9394@infradead.org \
--to=hch@infradead.org \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tim.t.walker@seagate.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;
as well as URLs for NNTP newsgroup(s).