From: keith.busch@linux.intel.com (Keith Busch)
Subject: How /dev/nvme numbers are allocated/mapped to BDF
Date: Fri, 3 Aug 2018 11:07:54 -0600 [thread overview]
Message-ID: <20180803170753.GB4551@localhost.localdomain> (raw)
In-Reply-To: <20180803165822.7ygbpvn3aqhe4aam@linux-x5ow.site>
On Fri, Aug 03, 2018@06:58:22PM +0200, Johannes Thumshirn wrote:
> On Fri, Aug 03, 2018@10:54:11AM -0600, Keith Busch wrote:
> > > [root at g-prime mrnuke]# nvme list
> > > Node SN Model Namespace Usage Format FW Rev
> > > ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
> > > /dev/nvme0n1 PHLF7363029G1P0GGN Dell Express Flash NVMe P4500 1.0TB SFF 1 1.00 TB / 1.00 TB 512 B + 0 B QDV1DP12
> > > /dev/nvme1n1 PHLE7260008Z3P2EGN Dell Express Flash NVMe P4600 3.2TB SFF 1 3.20 TB / 3.20 TB 512 B + 0 B QDV1DP12
> > > /dev/nvme2n1 S39YNX0HB00195 Dell Express Flash PM1725a 800GB SFF 1 800.17 GB / 800.17 GB 512 B + 0 B 1.0.4
> > > /dev/nvme3n1 S39YNX0HB00293 Dell Express Flash PM1725a 800GB SFF 1 800.17 GB / 800.17 GB 512 B + 0 B 1.0.4
> >
> > The sammy drives do not have compliant serial number. Spec requires
> > strings are left justified, padding spaces to the right.
>
> OMG, do we need quirks for serial numbers now?
I don't think linux cares as long as they're unique. It just looks weird.
next prev parent reply other threads:[~2018-08-03 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 22:09 How /dev/nvme numbers are allocated/mapped to BDF Alex_Gagniuc
2018-08-03 7:18 ` Christoph Hellwig
2018-08-03 14:40 ` Keith Busch
2018-08-03 16:16 ` Alex_Gagniuc
2018-08-03 16:54 ` Keith Busch
2018-08-03 16:58 ` Johannes Thumshirn
2018-08-03 17:07 ` Keith Busch [this message]
2018-08-03 17:20 ` Alex_Gagniuc
2018-08-03 17:40 ` Keith Busch
2018-08-04 8:16 ` Christoph Hellwig
2018-08-05 15:48 ` Alex_Gagniuc
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=20180803170753.GB4551@localhost.localdomain \
--to=keith.busch@linux.intel.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 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.