linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: axboe@kernel.dk, ming.lei@redhat.com, osandov@fb.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Setting up default iosched in 5.0+
Date: Fri, 24 May 2019 10:46:54 -0400	[thread overview]
Message-ID: <x49ftp329lt.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20190518093310.GA3123@avx2> (Alexey Dobriyan's message of "Sat, 18 May 2019 12:33:11 +0300")

Hi, Alexey,

Alexey Dobriyan <adobriyan@gmail.com> writes:

> 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?

A global parameter was never a good idea, because systems often have
different types of storage installed which benefit from different I/O
schedulers.  The goal is for the default to just work.

If you feel that the defaults don't work for you, then udev rules are
the way to go.

If you also feel that you really do want to set the default for all
devices, then you can use the following udev rule to emulate the old
elevator= kernel command line parameter:

https://github.com/lnykryn/systemd-rhel/blob/rhel-8.0.0/rules/40-elevator.rules

Cheers,
Jeff

  reply	other threads:[~2019-05-24 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18  9:33 Setting up default iosched in 5.0+ Alexey Dobriyan
2019-05-24 14:46 ` Jeff Moyer [this message]
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=x49ftp329lt.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=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 \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).