From mboxrd@z Thu Jan 1 00:00:00 1970 From: jthumshirn@suse.de (Johannes Thumshirn) Date: Mon, 4 Jun 2018 14:48:30 +0200 Subject: [PATCH 0/3] Provide more fine grained control over multipathing In-Reply-To: <29bfbc6c-861d-0348-2f8b-e803acad43ea@grimberg.me> References: <20180525135813.GB9591@redhat.com> <20180530220206.GA7037@redhat.com> <20180531163311.GA30954@lst.de> <20180531181757.GB11848@redhat.com> <20180601042441.GB14244@redhat.com> <0a0d4ff8-fe06-5869-cd18-a8c99b5e86f6@grimberg.me> <20180603160626.GA4361@redhat.com> <29bfbc6c-861d-0348-2f8b-e803acad43ea@grimberg.me> Message-ID: <20180604124829.pnpzt6vgijmrtfty@linux-x5ow.site> On Mon, Jun 04, 2018@02:46:47PM +0300, Sagi Grimberg wrote: > I agree with Christoph that changing personality on the fly is going to > be painful. This opt-in will need to be one-host at connect time. For > that, we will probably need to also expose an argument in nvme-cli too. > Changing the mpath personality will need to involve disconnecting the > controller and connecting again with the argument toggled. I think this > is the only sane way to do this. If we still want to make it dynamically, yes. I've raised this concern while working on the patch as well. > Another path we can make progress in is user visibility. We have > topology in place and you mentioned primary path (which we could > probably add). What else do you need for multipath-tools to support > nvme? I think the first priority is getting nvme notion into multipath-tools like I said elsewhere and then see. Martin Wilck was already working on patches for this. -- Johannes Thumshirn Storage jthumshirn at suse.de +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