[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181116101752.GA21531@lst.de>
Date: Fri, 16 Nov 2018 11:17:52 +0100
From: Christoph Hellwig <hch@....de>
To: Hannes Reinecke <hare@...e.de>
Cc: Christoph Hellwig <hch@....de>, Mike Snitzer <snitzer@...hat.com>,
linux-nvme@...ts.infradead.org,
Keith Busch <keith.busch@...el.com>,
Sagi Grimberg <sagi@...mberg.me>, axboe@...nel.dk,
Martin Wilck <mwilck@...e.com>, lijie <lijie34@...wei.com>,
xose.vazquez@...il.com, chengjike.cheng@...wei.com,
shenhong09@...wei.com, dm-devel@...hat.com,
wangzhoumengjian@...wei.com, christophe.varoqui@...nsvc.com,
bmarzins@...hat.com, sschremm@...app.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvme: allow ANA support to be independent of native
multipathing
On Fri, Nov 16, 2018 at 11:06:32AM +0100, Hannes Reinecke wrote:
> Ok, so would you be happy with making ANA support configurable?
I've looked a bit over the whole situation, and what I think we need
to do is:
a) warn if we see a ANA capable device without multipath support
so people know it is not going to work properly.
b) deprecate the multipath module option. It was only intended as
a migration for any pre-existing PCIe multipath user if there
were any, not to support any new functionality. So for 4.20
put in a patch that prints a clear warning when it is used,
including a link to the nvme list, and then for 4.25 or so
remove it entirely unless something unexpected come up.
This whole drama of optional multipath use has wasted way too much
of everyones time already.
Powered by blists - more mailing lists