On Thu, Jan 04 2018 at 6:47pm -0500, Keith Busch <keith.busch@xxxxxxxxx> wrote: > On Thu, Jan 04, 2018 at 06:36:27PM -0500, Mike Snitzer wrote: > > Right, I dropped that patch since it'd have only resulted in conflicts > > come merge time. As such, this series can easily go through the nvme > > tree to Jens. > > It looks like you can also touch up dm to allow it to multipath nvme > even if CONFIG_NVME_MULTIPATH is set. It may be useful since native NVMe > doesn't multipath namespaces across subsystems, and some crack smoking > people want to create something that requires that. I had a "CONFIG_NVME_MULITIPATH=Y" typo in the dm-mpath.c commit that added the CONFIG_NVME_MULTIPATH mutual exclussion in dm-4.16; so I just dropped it via rebase. So now the underlying nvme devices (already multipath'd by NVMe) should be discoverable by multipathd. Who am I to judge crack smokers?
