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.2.3 for 2.6.12 and 2.6.13-rc3
Date: Mon, 18 Jul 2005 16:40:46 +1000 [thread overview]
Message-ID: <42DB4EEE.2020900@bigpond.net.au> (raw)
This version contains minor bug fixes and improvements to spa_no_frills
and zaphod schedulers including changes to the default configuration
parameters for zaphod that take into account the results of tests using
Con Kolivas's new (and very useful) interbench benchmark tool.
A patch from Plugsched-5.2.2 to PlugSched-5.2.3 for 2.6.12 is available at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-5.2.2-to-5.2.3-for-2.6.12.patch?download>
and a full patch for 2.6.13-rc3 is available at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-5.2.3-for-2.6.13-rc3.patch?download>
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
next reply other threads:[~2005-07-18 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 6:40 Peter Williams [this message]
2005-07-22 7:14 ` [ANNOUNCE][RFC] PlugSched-5.2.3 for 2.6.12 and 2.6.13-rc3 Peter Williams
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=42DB4EEE.2020900@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