[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180604071829.tq7wmx4bvk4uzubd@linux-x5ow.site>
Date: Mon, 4 Jun 2018 09:18:29 +0200
From: Johannes Thumshirn <jthumshirn@...e.de>
To: Hannes Reinecke <hare@...e.de>
Cc: Jens Axboe <axboe@...nel.dk>, Mike Snitzer <snitzer@...hat.com>,
Christoph Hellwig <hch@....de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Linux NVMe Mailinglist <linux-nvme@...ts.infradead.org>,
Laurence Oberman <loberman@...hat.com>,
Sagi Grimberg <sagi@...mberg.me>,
James Smart <james.smart@...adcom.com>,
Ewan Milne <emilne@...hat.com>,
Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>,
Keith Busch <keith.busch@...el.com>,
Martin George <marting@...app.com>,
John Meneghini <John.Meneghini@...app.com>,
dm-devel@...hat.com, mwilck@...e.de
Subject: Re: [PATCH 0/3] Provide more fine grained control over multipathing
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@...e.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
Powered by blists - more mailing lists