On Mon, Jun 04, 2018 at 08:19:21AM +0200, Hannes Reinecke wrote: > Without it we're having a choice of disappointing (paying) customers or > disappointing the upstream community. I personally think (regardless of the fact, that I wrote the patch under discussion), using the module parameter is sufficient for these kind of customers. For me it's an either/or kind of setting (either native or dm-mpath). Downstream distributions could still carry a small patch flipping the default to off if they want to maintain backwards compatibility with existing dm-mpath setups (which for NVMe I doubt there are many!). What we really should do is, try to give multipath-tools a 'nvme list-subsys' like view of nvme native multipathing (and I think Martin W. has already been looking into this a while ago). Johannes -- Johannes Thumshirn Storage jthumshirn@xxxxxxx +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
