Linux-Block Archive on lore.kernel.org
 help / color / Atom feed
* Setting up default iosched in 5.0+
@ 2019-05-18  9:33 Alexey Dobriyan
  2019-05-24 14:46 ` Jeff Moyer
  0 siblings, 1 reply; 4+ messages in thread
From: Alexey Dobriyan @ 2019-05-18  9:33 UTC (permalink / raw)
  To: axboe, ming.lei, osandov; +Cc: linux-block, linux-kernel

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?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Setting up default iosched in 5.0+
  2019-05-18  9:33 Setting up default iosched in 5.0+ Alexey Dobriyan
@ 2019-05-24 14:46 ` Jeff Moyer
  2019-05-24 15:38   ` Paolo Valente
  2019-05-24 18:25   ` Alexey Dobriyan
  0 siblings, 2 replies; 4+ messages in thread
From: Jeff Moyer @ 2019-05-24 14:46 UTC (permalink / raw)
  To: Alexey Dobriyan; +Cc: axboe, ming.lei, osandov, linux-block, linux-kernel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Setting up default iosched in 5.0+
  2019-05-24 14:46 ` Jeff Moyer
@ 2019-05-24 15:38   ` Paolo Valente
  2019-05-24 18:25   ` Alexey Dobriyan
  1 sibling, 0 replies; 4+ messages in thread
From: Paolo Valente @ 2019-05-24 15:38 UTC (permalink / raw)
  To: Jeff Moyer
  Cc: Alexey Dobriyan, Jens Axboe, Ming Lei, Omar Sandoval,
	linux-block, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]



> Il giorno 24 mag 2019, alle ore 16:46, Jeff Moyer <jmoyer@redhat.com> ha scritto:
> 
> 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.
> 

Just for completeness, the current default is the worst possible
choice on all systems with a speed below 500 KIOPS, which includes
practically all personal systems ;) But this is a different story ...

Thanks,
Paolo

> 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


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Setting up default iosched in 5.0+
  2019-05-24 14:46 ` Jeff Moyer
  2019-05-24 15:38   ` Paolo Valente
@ 2019-05-24 18:25   ` Alexey Dobriyan
  1 sibling, 0 replies; 4+ messages in thread
From: Alexey Dobriyan @ 2019-05-24 18:25 UTC (permalink / raw)
  To: Jeff Moyer; +Cc: axboe, ming.lei, osandov, linux-block, linux-kernel

On Fri, May 24, 2019 at 10:46:54AM -0400, Jeff Moyer wrote:
> 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.

Kernel can by default complain about "noop" for HDD disks and setup
"noop" for SSD. And then let admins customise it further.

> 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

The following udev rules seem to work, thanks:

	$ cat /etc/udev/rules.d/01-iosched.rules
	SUBSYSTEM=="block", ACTION=="add", KERNEL=="sda", ATTR{queue/scheduler}="bfq"
	SUBSYSTEM=="block", ACTION=="add", KERNEL=="sdb", ATTR{queue/scheduler}="bfq"

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-18  9:33 Setting up default iosched in 5.0+ Alexey Dobriyan
2019-05-24 14:46 ` Jeff Moyer
2019-05-24 15:38   ` Paolo Valente
2019-05-24 18:25   ` Alexey Dobriyan

Linux-Block Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-block/0 linux-block/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-block linux-block/ https://lore.kernel.org/linux-block \
		linux-block@vger.kernel.org linux-block@archiver.kernel.org
	public-inbox-index linux-block


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-block


AGPL code for this site: git clone https://public-inbox.org/ public-inbox