Re: nvme: allow ANA support to be independent of native multipathing

2018-11-19 Thread Mike Snitzer
On Mon, Nov 19 2018 at 4:39am -0500, Christoph Hellwig wrote: > 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

Re: nvme: allow ANA support to be independent of native multipathing

2018-11-19 Thread Mike Snitzer
On Mon, Nov 19 2018 at 4:39am -0500, Christoph Hellwig wrote: > 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

Re: nvme: allow ANA support to be independent of native multipathing

2018-11-19 Thread Christoph Hellwig
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

Re: nvme: allow ANA support to be independent of native multipathing

2018-11-19 Thread Christoph Hellwig
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