linux-kernel - Setting up default iosched in 5.0+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 18 May 2019 12:33:11 +0300
From:   Alexey Dobriyan <adobriyan@...il.com>
To:     axboe@...nel.dk, ming.lei@...hat.com, osandov@...com
Cc:     linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Setting up default iosched in 5.0+

5.0 deleted three io schedulers and more importantly CONFIG_DEFAULT_IOSCHED
option:

	commit f382fb0bcef4c37dc049e9f6963e3baf204d815c
	block: remove legacy IO schedulers

After figuring out that I silently became "noop" customer enabling just
BFQ didn't work: "noop" is still being selected by default.

There is an "elevator=" command line option but it does nothing.

Are users supposed to add stuff to init scripts now?