From: hch@infradead.org (Christoph Hellwig)
Subject: Devices expected?
Date: Tue, 11 Sep 2018 00:23:17 -0700 [thread overview]
Message-ID: <20180911072317.GA17437@infradead.org> (raw)
In-Reply-To: <20180907155524.GA857@localhost.localdomain>
On Fri, Sep 07, 2018@09:55:25AM -0600, Keith Busch wrote:
> > Does nvme2c1n1 represent one path for the nvme2n1 device to use? If I connected a second path I would see something like nvme2c2n1 pop up as well?
>
> Yes, that is what that those names represent.
>
> In your example, the '2' in nvme2 is the subsystem instance, which
> is just a unique number software assigned to the subsystem. The '1'
> in nvme2c1 is the controller id that identify controller reports, so it
> may not necessarily start at 1 or increase sequentially.
Also note that we will only use the multipath code if the namespace
is marked as shared namespace in NMIC. For private namespaces we
skip the multipath detection.
prev parent reply other threads:[~2018-09-11 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 20:26 Devices expected? Gruher, Joseph R
2018-09-06 21:05 ` Keith Busch
2018-09-07 15:40 ` Gruher, Joseph R
2018-09-07 15:55 ` Keith Busch
2018-09-11 7:23 ` 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=20180911072317.GA17437@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;
as well as URLs for NNTP newsgroup(s).