From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [PATCH RFC] nvme: Common subsys and controller instances IDA
Date: Thu, 16 May 2019 10:58:43 -0400 [thread overview]
Message-ID: <yq17eaqbg4c.fsf@oracle.com> (raw)
In-Reply-To: <20190516144452.GB23372@localhost.localdomain> (Keith Busch's message of "Thu, 16 May 2019 08:44:52 -0600")
Keith,
>> to keep in line with the other symlinks in /dev/disk/by-id/ The
>> controller symlinks don't really fall into this category, though; we
>> could create a 'nvme' subdirectory (much like MD does), and create
>> symlinks in there.
>
> Cool, I would also like to see persistent char dev names, but I wasn't
> sure where they'd go. If we can make our own 'nvme' subdirectory,
> that'd be great.
Should be fine. As long as /dev/disk stays intact.
It would be really nice to have a clear indication of
subsys/controller/namespace relationships. So much confusion as a result
of the current approach...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-05-16 14:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 21:33 [PATCH RFC] nvme: Common subsys and controller instances IDA Keith Busch
2019-05-16 6:46 ` Christoph Hellwig
2019-05-16 7:03 ` Hannes Reinecke
2019-05-16 14:44 ` Keith Busch
2019-05-16 14:51 ` Christoph Hellwig
2019-05-16 14:58 ` Martin K. Petersen [this message]
2019-05-21 9:54 ` Max Gurtovoy
2019-05-21 14:35 ` Keith Busch
2019-05-21 14:51 ` Max Gurtovoy
2019-05-21 14:58 ` Keith Busch
2019-05-24 8:03 ` Sagi Grimberg
2019-05-24 14:07 ` Keith Busch
2019-05-24 16:17 ` Sagi Grimberg
2019-05-24 19:14 ` Max Gurtovoy
2019-05-24 23:23 ` Sagi Grimberg
2019-05-24 23:30 ` Keith Busch
2019-05-16 14:40 ` Keith Busch
2019-05-16 14:57 ` Keith Busch
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=yq17eaqbg4c.fsf@oracle.com \
--to=martin.petersen@oracle.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