From: Keith Busch <kbusch@kernel.org>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"jay.vosburgh@canonical.com" <jay.vosburgh@canonical.com>,
Dan Streetman <dan.streetman@canonical.com>
Subject: Re: [PATCH] nvme: Use first ctrl->instance id as subsystem id
Date: Wed, 14 Aug 2019 13:08:15 -0600 [thread overview]
Message-ID: <20190814190814.GC3256@localhost.localdomain> (raw)
In-Reply-To: <b5b471cc-8935-cf96-d55a-a7dc731cb0d6@canonical.com>
On Wed, Aug 14, 2019 at 11:29:17AM -0700, Guilherme G. Piccoli wrote:
> It is a suggestion from my colleague Dan (CCed here), something like:
> for non-multipath nvme, keep nvmeC and nvmeCnN (C=controller ida,
> N=namespace); for multipath nvme, use nvmeScCnN (S=subsystem ida).
This will inevitably lead to collisions. The existing naming scheme was
selected specifically to avoid that problem.
WARNING: multiple messages have this Message-ID (diff)
From: kbusch@kernel.org (Keith Busch)
Subject: [PATCH] nvme: Use first ctrl->instance id as subsystem id
Date: Wed, 14 Aug 2019 13:08:15 -0600 [thread overview]
Message-ID: <20190814190814.GC3256@localhost.localdomain> (raw)
In-Reply-To: <b5b471cc-8935-cf96-d55a-a7dc731cb0d6@canonical.com>
On Wed, Aug 14, 2019@11:29:17AM -0700, Guilherme G. Piccoli wrote:
> It is a suggestion from my colleague Dan (CCed here), something like:
> for non-multipath nvme, keep nvmeC and nvmeCnN (C=controller ida,
> N=namespace); for multipath nvme, use nvmeScCnN (S=subsystem ida).
This will inevitably lead to collisions. The existing naming scheme was
selected specifically to avoid that problem.
next prev parent reply other threads:[~2019-08-14 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 14:28 [PATCH] nvme: Use first ctrl->instance id as subsystem id Guilherme G. Piccoli
2019-08-14 14:28 ` Guilherme G. Piccoli
2019-08-14 16:06 ` Keith Busch
2019-08-14 16:06 ` Keith Busch
2019-08-14 16:18 ` Guilherme G. Piccoli
2019-08-14 16:18 ` Guilherme G. Piccoli
2019-08-14 16:27 ` Keith Busch
2019-08-14 16:27 ` Keith Busch
2019-08-14 18:29 ` Guilherme G. Piccoli
2019-08-14 18:29 ` Guilherme G. Piccoli
2019-08-14 19:08 ` Keith Busch [this message]
2019-08-14 19:08 ` Keith Busch
2019-08-15 13:01 ` Guilherme G. Piccoli
2019-08-15 13:01 ` Guilherme G. Piccoli
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=20190814190814.GC3256@localhost.localdomain \
--to=kbusch@kernel.org \
--cc=axboe@fb.com \
--cc=dan.streetman@canonical.com \
--cc=gpiccoli@canonical.com \
--cc=hch@lst.de \
--cc=jay.vosburgh@canonical.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.