On Fri, Nov 16, 2018 at 02:28:02PM -0500, Mike Snitzer wrote: > You rejected the idea of allowing fine-grained control over whether > native NVMe multipathing is enabled or not on a per-namespace basis. > All we have is the coarse-grained nvme_core.multipath=N knob. Now > you're forecasting removing even that. Please don't do that. The whole point is that this hook was intended as a band aid for the hypothetical pre-existing setups. Not ever for new development. > Please, PLEASE take v2 of this patch.. please? ;) See the previous mail for the plan ahead. I'm sick and tired of you trying to sneak your new developemts back in.
