Why BFQ scheduler available only for NVMe device?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry I don't finded answer on my question.
Why BFQ scheduler available only for NVMe device?

$ find /sys -name scheduler -exec grep . {} +
find: ‘/sys/kernel/debug’: Permission denied
find: ‘/sys/fs/pstore’: Permission denied
find: ‘/sys/fs/bpf’: Permission denied
/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.1/ata5/host4/target4:0:0/4:0:0:0/block/sda/queue/scheduler:noop
deadline [cfq]
/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/queue/scheduler:[none]
mq-deadline bfq
/sys/devices/pci0000:00/0000:00:07.1/0000:0c:00.3/usb4/4-3/4-3.4/4-3.4.1/4-3.4.1:1.0/host9/target9:0:0/9:0:0:0/block/sdb/queue/scheduler:noop
deadline [cfq]

$ uname -r
4.19.0-0.rc5.git3.1.fc30.x86_64

$ cat /boot/config-`uname -r` | grep -i bfq
CONFIG_IOSCHED_BFQ=m
CONFIG_BFQ_GROUP_IOSCHED=y


--
Best Regards,
Mike Gavrilov.




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux