From: kbusch@kernel.org (Keith Busch)
Subject: [RFC/PATCH nvme-cli] nvme list- separate controllers from namespaces
Date: Wed, 15 May 2019 08:14:48 -0600 [thread overview]
Message-ID: <20190515141448.GA21433@localhost.localdomain> (raw)
In-Reply-To: <EB8F1E865882C64ABCEDE282942116B98F467B@FMSMSX102.amr.corp.intel.com>
On Wed, May 01, 2019@08:09:55PM +0000, Tay, Kelly wrote:
> Separated controllers from namespaces on nvme list
> -controller that is not enumerating namespaces is still represented to resolve confusion around missing devices
> -prevents duplicate printing of data
>
> Signed-off-by: Kelly Tay <kelly.tay at intel.com>
The only problem is that we've lost the serial number on the namespace
output, and since multipathing naming conventions doesn't mean
/dev/nvme0 is the controller for namespace /dev/nvme0n1, it is just
going to be that much more confusing for people to match up which
namespace goes with which controller.
I'd still like to take this anyway, but I may have to make some
modifications on top of this. Perhaps a ',' separate lest of controllers
that go with the namespace would be okay.
prev parent reply other threads:[~2019-05-15 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 20:09 [RFC/PATCH nvme-cli] nvme list- separate controllers from namespaces Tay, Kelly
2019-05-01 22:48 ` Chaitanya Kulkarni
2019-05-08 21:46 ` Reese, Benjamin
2019-05-15 14:14 ` Keith Busch [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=20190515141448.GA21433@localhost.localdomain \
--to=kbusch@kernel.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