All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: linux-kernel@vger.kernel.org
Cc: Nick Warne <nick@linicks.net>, Jens Axboe <axboe@suse.de>
Subject: Re: scheduler question 2.6.16.x
Date: Wed, 26 Apr 2006 20:09:06 +0200	[thread overview]
Message-ID: <444FB742.40604@tomt.net> (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?

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

  parent reply	other threads:[~2006-04-26 18:08 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 [this message]
2006-04-26 18:33       ` Nick Warne
2006-04-27 21:39     ` Bill Davidsen

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=444FB742.40604@tomt.net \
    --to=andre@tomt.net \
    --cc=axboe@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.