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 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
