On 1/31/23 00:52, Linus Walleij wrote:
If we enable the memory stick block layer, use Kconfig to imply the BFQ I/O scheduler. As all memstick devices are single-queue, this is the scheduler that users want so let's be helpful and make sure it gets default-selected into a manual kernel configuration. It will still need to be enabled at runtime (usually with udev scripts).
Do users really want the BFQ scheduler? Has performance of BFQ been compared with iocost (CONFIG_BLK_CGROUP_IOCOST)? My colleagues are using iocost instead of BFQ in resource-constrained environments.
Bart.
