scheduler question 2.6.16.x
Hi all,
I see in menuconfig I have two options:
<*> Anticipatory I/O scheduler
<*> Deadline I/O scheduler
Help reveals Anticipatory is pretty good, but make a slightly larger kernel - Deadline help says it a good alternative to Anticipatory.
But I can build both in... so I guess then the kernel decides what is the best to use? Or should it be so I am only allowed to select one or the other and allowing both is an oversight?
Thanks,
Nick
Signature · 2 lines
"Person who say it cannot be done should not interrupt person doing it." -Chinese Proverb
Quoted 7 lines · Nick Warne
Hi all,
I see in menuconfig I have two options:
<*> Anticipatory I/O scheduler
<*> Deadline I/O scheduler
Quoted 6 lines
Help reveals Anticipatory is pretty good, but make a slightly larger kernel - Deadline help says it a good alternative to Anticipatory.
But I can build both in... so I guess then the kernel decides what is the best to use? Or should it be so I am only allowed to select one or the other and allowing both is an oversight?
See the option no more than two lines down from that, default io scheduler. Also see Documentation/block/switching-sched.txt and/or Documentation/kernel-parameters.txt (elevator=) section.
Signature · 1 line
Jens Axboe
Quoted 7 lines · Jens Axboe
Quoted 3 lines
But I can build both in... so I guess then the kernel decides what is the best to use? Or should it be so I am only allowed to select one or the other and allowing both is an oversight?
See the option no more than two lines down from that, default io scheduler. Also see
Documentation/block/switching-sched.txtand/orDocumentation/kernel-parameters.txt(elevator=) section.
Hi Jens,
I haven't got the switching-sched.txt, although I found a sched-design.txt... but what I meant was if I select whatever default, do/can I still need to select either/or scheduler?
i.e. why doesn't 'default selection option' only allow that scheduler to be selected?
Nick
Signature · 2 lines
"Person who say it cannot be done should not interrupt person doing it." -Chinese Proverb
Quoted 10 lines · Nick Warne
Quoted 7 lines · Jens Axboe
Quoted 3 lines
But I can build both in... so I guess then the kernel decides what is the best to use? Or should it be so I am only allowed to select one or the other and allowing both is an oversight?
See the option no more than two lines down from that, default io scheduler. Also see
Documentation/block/switching-sched.txtand/orDocumentation/kernel-parameters.txt(elevator=) section.
Quoted 8 lines
Hi Jens,
I haven't got the switching-sched.txt, although I found a sched-design.txt... but what I meant was if I select whatever default, do/can I still need to select either/or scheduler?
i.e. why doesn't 'default selection option' only allow that scheduler to be selected?
I don't understand your question, but here's how it works. You can select as many/few schedulers as you want. You can only set a scheduler default, if it's compiled in (y, not m). If you don't select any schedulers, noop is still selected and wil be the default.
Just try the options, you'll see how they work...
Signature · 1 line
Jens Axboe
Quoted 9 lines · Nick Warne
Quoted 6 lines · Jens Axboe
Quoted 3 lines
But I can build both in... so I guess then the kernel decides what is the best to use? Or should it be so I am only allowed to select one or the other and allowing both is an oversight?
See the option no more than two lines down from that, default io scheduler. Also see
Documentation/block/switching-sched.txtand/orDocumentation/kernel-parameters.txt(elevator=) section.
Quoted 5 lines
Hi Jens,
I haven't got the switching-sched.txt, although I found a sched-design.txt... but what I meant was if I select whatever default, do/can I still need to select either/or scheduler?
i.e. why doesn't 'default selection option' only allow that scheduler to be selected?
That would be a artificial (and silly!) limit - the io-scheduler is pluggable and selectable at boot, you can even change it at run time at a per block device level.
See the elevator= boot option and /sys/block/<device>/queue/scheduler
Quoted 8 lines · Andre Tomt
Quoted 2 lines
i.e. why doesn't 'default selection option' only allow that scheduler to be selected?
That would be a artificial (and silly!) limit - the io-scheduler is pluggable and selectable at boot, you can even change it at run time at a per block device level.
See the elevator= boot option and /sys/block/<device>/queue/scheduler
Ohh! I see. That is what I was sort of asking (but didn't know what precisely to ask)... OK thanks, understand now.
Nick
Signature · 2 lines
"Person who say it cannot be done should not interrupt person doing it." -Chinese Proverb
Quoted 9 lines · Nick Warne
Quoted 6 lines · Jens Axboe
Quoted 3 lines
But I can build both in... so I guess then the kernel decides what is the best to use? Or should it be so I am only allowed to select one or the other and allowing both is an oversight?
See the option no more than two lines down from that, default io scheduler. Also see
Documentation/block/switching-sched.txtand/orDocumentation/kernel-parameters.txt(elevator=) section.
Quoted 5 lines
Hi Jens,
I haven't got the switching-sched.txt, although I found a sched-design.txt... but what I meant was if I select whatever default, do/can I still need to select either/or scheduler?
i.e. why doesn't 'default selection option' only allow that scheduler to be selected?
Not clear is you mean "allow that to the the only selection" which it does, or "only allow that selection" which makes no sense, you can boot using any compiled scheduler.
My configuration for beverage is set to "cask conditioned IPA" but I have most of the "Microbrewed" selections for IPA, PA, Stout and Porter compiled in. The "bland American and imported brews" section is disabled, with "water" enabled as a module.
The preference is what you use by default, but not an irrevocable choice.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me