[PATCH 3/6] nvme: claim block devices

Hannes Reinecke hare at suse.com
Thu Oct 5 07:39:23 PDT 2017


On 10/05/2017 04:05 PM, Keith Busch wrote:
> On Thu, Oct 05, 2017 at 08:51:24AM +0200, Johannes Thumshirn wrote:
>> On Wed, Oct 04, 2017 at 09:08:57PM -0400,  Martin K. Petersen  wrote:
>>>
>>> Christoph,
>>>
>>>> The only other option I could think of would be to turn names around:
>>>> make /dev/nvmeX (chardev) and /dev/nvmeXnY the per-subsystem devices
>>>> that are multipathed if available.  We'd then need new devices for the
>>>> invdividual controllers.
>>>
>>> I like that approach.
>>
>> /me too
> 
> I can get on board with this approach for the namespaces, but the
> controller char devs should stay as they are for compatibility and
> existing tools. The IO commands (including reservations) are not
> controller specific, so not knowing which path is used will okay for
> namespaces. Most admin commands are controller specific, so we can't
> just shift the controller handle to the subsystem level.
> 
I'm fine with having individual char devs for the controller and the
namespaces. That was the plan anyway, and they don't get into play with
systemd et al.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare at suse.com			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)



More information about the Linux-nvme mailing list