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>,
Jake Moilanen <moilanen@austin.ibm.com>
Subject: [ANNOUNCE][RFC] PlugSched-6.1 for 2.6.13
Date: Wed, 31 Aug 2005 10:46:07 +1000 [thread overview]
Message-ID: <4314FDCF.3050502@bigpond.net.au> (raw)
This version contains a modified spa_ws scheduler with a more persistent
bonus mechanism. Although the "bonus only at wake up" mechanism of the
original worked well on the first systems it was tested on (an old SMP
system and a 3GHz SMT system) subsequent tests on a 2GHz single
processor system were disappointing. (Apart from a bug in the original
implementation) the primary reason for this was that the X server was
not always able to complete its work in the first time slice after
waking and had to try and complete it without the benefit of the bonus
which causes obvious delays when the system is loaded. The new
mechanism is a simplification of the persistent interactive bonus
mechanism in zaphod.
A patch for 2.6.13 is available at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1-for-2.6.13.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, spa_ws 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-08-31 0:46 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=4314FDCF.3050502@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moilanen@austin.ibm.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