update NVMe multipath to conditionally claim controllers
Subsystems (2)
I'd like to have the same Linux kernel be able to use either NVMe's native multipath or DM multipath.
Should be relatively simple to filter which controllers can/cannot be claimed by NVMe multipathing (without having to resort to the big hammer of CONFIG_NVME_MULTIPATH).
I'd like to understand what is the preferred disposition of the filter list (black or white)? I assume having a blacklist would be more inkeeping with Christoph's desire for NVMe to be the default for NVMe multipathing. But that disposition aside, not sure if there are other issues that should influence implementing more flexible use of NVMe resources.
Thanks,
Mike
Quoted 7 lines · Mike Snitzer
I'd like to have the same Linux kernel be able to use either NVMe's native multipath or DM multipath.
Should be relatively simple to filter which controllers can/cannot be claimed by NVMe multipathing (without having to resort to the big hammer of
CONFIG_NVME_MULTIPATH).
Quoted 7 lines
I'd like to understand what is the preferred disposition of the filter list (black or white)? I assume having a blacklist would be more inkeeping with Christoph's desire for NVMe to be the default for NVMe multipathing. But that disposition aside, not sure if there are other issues that should influence implementing more flexible use of NVMe resources.
+1
The discussion here is not so much about the technical merits but rather about the customer/admin expectations.
Some customers have quite some elaborate tooling around provisioning etc, so they will be putting up support calls with us if those fail to work with NVMe.
Cheers,
Hannes
Signature · 10 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg) -- dm-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/dm-devel