LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: axboe@kernel.dk, ming.lei@redhat.com, osandov@fb.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Setting up default iosched in 5.0+
Date: Sat, 18 May 2019 12:33:11 +0300 [thread overview]
Message-ID: <20190518093310.GA3123@avx2> (raw)
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?
next reply other threads:[~2019-05-18 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 9:33 Alexey Dobriyan [this message]
2019-05-24 14:46 ` Jeff Moyer
2019-05-24 15:38 ` Paolo Valente
2019-05-24 18:25 ` Alexey Dobriyan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190518093310.GA3123@avx2 \
--to=adobriyan@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--subject='Re: Setting up default iosched in 5.0+' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).