mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: "Søren Lott" <soren3@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chris Han <xiphux@gmail.com>, Con Kolivas <kernel@kolivas.org>,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [ANNOUNCE][RFC] PlugSched-5.0 for 2.6.11, 2.6.12-rc4 and 2.6.12-rc4-mm2
Date: Tue, 24 May 2005 12:04:23 +1000	[thread overview]
Message-ID: <42928BA7.9040001@bigpond.net.au> (raw)
In-Reply-To: <200505232217.33960.soren3@gmail.com>

Søren Lott wrote:
> On Monday 23 May 2005 21:38, Peter Williams wrote:
> 
>>A patch of PlugSched-5.0 (containing ingosched, nicksched, staircase,
>>spa_no_frills and zaphod CPU schedulers) against a 2.6.11 kernel is
>>available for download from:
> 
> 
> Does it have any documentation ?

Only that in th KConfig files. :-(

It's fairly simple really.  You can select a default scheduler at kernel 
build time.  If you wish to boot with a scheduler other than the default 
it can be selected at boot time by adding:

cpusched=<scheduler>

to the boot command line where <scheduler> is one of: ingosched, 
nicksched, staircase, spa_no_frills or zaphod.  If you don't change the 
default when you build the kernel the default scheduler will be 
ingosched (which is the normal scheduler).

The scheduler in force on a running system can be determined by the 
contents of:

/proc/scheduler

Control parameters for the scheduler can be read/set via files in:

/sys/cpusched/<scheduler>/

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

      reply	other threads:[~2005-05-24  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24  0:38 Peter Williams
2005-05-24  1:17 ` Søren Lott
2005-05-24  2:04   ` Peter Williams [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=42928BA7.9040001@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soren3@gmail.com \
    --cc=wli@holomorphy.com \
    --cc=xiphux@gmail.com \
    /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

all inboxes | Powered by JetHome®