From: Bill Davidsen <davidsen@tmr.com>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scheduler question 2.6.16.x
Date: Thu, 27 Apr 2006 17:39:24 -0400 [thread overview]
Message-ID: <44513A0C.3020403@tmr.com> (raw)
In-Reply-To: <200604251933.48363.nick@linicks.net>
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?
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.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2006-04-27 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 18:05 scheduler question 2.6.16.x Nick Warne
2006-04-25 18:15 ` Jens Axboe
2006-04-25 18:33 ` Nick Warne
2006-04-25 18:51 ` Jens Axboe
2006-04-26 18:09 ` Andre Tomt
2006-04-26 18:33 ` Nick Warne
2006-04-27 21:39 ` Bill Davidsen [this message]
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=44513A0C.3020403@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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).