On 07/14/2017 12:40 AM, Johannes Thumshirn wrote: > On Thu, Jul 13, 2017 at 08:02:41AM -0600, Jens Axboe wrote: >> Because it sucks as an interface - there's no way to apply different >> settings to different devices, and using the kernel command line to >> control something like this is ugly. It never should have been done. >> >> The sysfs interface, either manually, scripted, or through udev, >> makes a lot more sense. > > Not that I disagree with your reasons, but not being able to select a > mq scheduler confuses quite some users out there. Maybe we can add something about the API being deprecated, if someone tries to select an mq scheduler. The old scheduler will die in due course once that path goes away, and once that happens, we can kill the parameter. -- Jens Axboe
