Messages in this thread | | | Date | Tue, 25 Apr 2006 20:51:42 +0200 | From | Jens Axboe <> | Subject | Re: scheduler question 2.6.16.x |
| |
On Tue, Apr 25 2006, Nick Warne wrote: > On Tuesday 25 April 2006 19:15, Jens Axboe wrote: > > > > 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. > > 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...
-- Jens Axboe
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |