[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <847276bd-5242-1434-5f41-75fedb900a32@suse.de>
Date: Tue, 14 Feb 2017 08:11:46 +0100
From: Hannes Reinecke <hare@...e.de>
To: Omar Sandoval <osandov@...ndov.com>
Cc: Jens Axboe <axboe@...nel.dk>,
Paolo Valente <paolo.valente@...aro.org>,
Tejun Heo <tj@...nel.org>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, ulf.hansson@...aro.org,
linus.walleij@...aro.org, broonie@...nel.org
Subject: Re: [PATCH BUGFIX] block: make elevator_get robust against cross
blk/blk-mq choice
On 02/14/2017 08:07 AM, Omar Sandoval wrote:
> On Tue, Feb 14, 2017 at 07:58:22AM +0100, Hannes Reinecke wrote:
>> While we're at the topic:
>>
>> Can't we use the same names for legacy and mq scheduler?
>> It's quite an unnecessary complication to have
>> 'noop', 'deadline', and 'cfq' for legacy, but 'none' and 'mq-deadline'
>> for mq. If we could use 'noop' and 'deadline' for mq, too, the existing
>> settings or udev rules will continue to work and we wouldn't get any
>> annoying and pointless warnings here...
>
> I mentioned this to Jens a little while ago but I didn't feel strongly
> enough to push the issue. I also like this idea -- it makes the
> transition to blk-mq a little more transparent.
>
And saves us _a lot_ of support cases :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@...e.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists