On Wed, 12 Dec 2018 16:50:10 -0700
Chris Murphy <lists(a)colorremedies.com> wrote:
OK that worked for an nvme drive, but not for an internal SATA HDD.
$ sudo lsmod | grep bfq
$ sudo cat /sys/block/sda/queue/scheduler
noop deadline [cfq]
$ sudo
insmod /usr/lib/modules/4.19.8-300.fc29.x86_64/kernel/block/bfq.ko.xz
$ sudo cat /sys/block/sda/queue/scheduler noop deadline [cfq]
$ sudo lsmod | grep bfq
bfq 69632 0
$
So yeah this seems a lot more difficult than it should be.
Thanks for the confirmation. I built all the schedulers into the
kernel. I made the assumption that the kernel would be aware of those
built in drivers. For deadline and cfq, true, for bfq, I thought it
was not true.
The plot thickens. I looked in the journal and found
localhost.localdomain kernel: io scheduler bfq registered
localhost.localdomain kernel: io scheduler cfq registered (default)
localhost.localdomain kernel: io scheduler deadline registered
localhost.localdomain kernel: io scheduler noop registered
So the kernel is aware of bfq. There must be something missing for bfq
in order for it to be treated the same as cfq or deadline.