mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Chris Han <xiphux@gmail.com>, Con Kolivas <kernel@kolivas.org>,
	William Lee Irwin III <wli@holomorphy.com>
Subject: [ANNOUNCE][RFC] PlugSched-5.1 for 2.6.11, 2.6.12-rc5 and 2.6.12-rc5-mm2
Date: Sun, 05 Jun 2005 15:42:25 +1000	[thread overview]
Message-ID: <42A290C1.1050106@bigpond.net.au> (raw)

A patch to upgrade PlugSched-5.0 to PlugSched-5.1 (containing ingosched, 
nicksched, staircase, spa_no_frills and zaphod CPU schedulers) against a 
2.6.11 kernel is available for download from:

<http://prdownloads.sourceforge.net/cpuse/plugsched-5.0-to-5.1-for-2.6.11.patch?download>

A patch of PlugSched-5.1 for 2.6.12-rc5 is at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-5.1-for-2.6.12-rc5.patch?download>

and for 2.6.12-rc5-mm2 at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-5.1-for-2.6.12-rc5-mm2.patch?download>

Version 5.1 contains bug fixes for spa_no_frills and zaphod, upgrade of 
staircase to version 11.2 and the recent changes Con Kolivas's "nice" 
aware load balancing patch.

Very Brief Documentation:

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-06-05  5:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42A290C1.1050106@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®