> Il giorno 13 lug 2017, alle ore 16:02, Jens Axboe <axboe@xxxxxxxxx> ha scritto: > > On 07/13/2017 04:11 AM, Johannes Thumshirn wrote: >> On Wed, Jul 12, 2017 at 04:51:33PM -0600, Jens Axboe wrote: >>> No, that boot option was a mistake, let's not propagate that to mq >>> scheduling as well. >> >> Can you please explain why? I as well have requests from our users to >> select the mq schedulers on the command line. > > 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. > One doubt: with the new interface, and using, I guess, udev, is it still possible to control which I/O scheduler is actually used during all the boot process, or at least almost all of it? Thanks, Paolo > -- > Jens Axboe >
