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: Re: [ANNOUNCE][RFC] PlugSched-6.1.3 for 2.6.13 and 2.6.14-rc4
Date: Sat, 29 Oct 2005 12:35:01 +1000 [thread overview]
Message-ID: <4362DFD5.2000709@bigpond.net.au> (raw)
In-Reply-To: <434F01EA.6060709@bigpond.net.au>
Peter Williams wrote:
> This version contains a new scheduler, spa_svr, which is a minor
> extension of spa_no_frills intended for use on servers. It makes no
> attempt to improve interactive responsiveness but includes a simplified
> version of the throughput bonus mechanism found in Zaphod. This
> mechanism attempts to minimize the time tasks spend on run queues
> waiting for CPU access when the system is moderately loaded by giving
> tasks temporary priority bonuses based on the relationship between the
> recent average time spent on run queues and on a cpu per cycle.
> (Although it's effectiveness tends to disappear when the system is fully
> loaded, it is still useful as considerable delay can be seen on systems
> with quite low average loads due to lack of serendipity.)
>
> A patch for 2.6.14-rc4 is available at:
>
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.3-for-2.6.14-rc4.patch?download>
>
>
> and a patch to upgrade the 6.1.2 version for 2.6.13 to 6.1.3 is
> available at:
>
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.2-to-6.1.3-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, spa_svr 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
A patch for the 2.6.14 official release kernel is now available at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.3-for-2.6.14.patch?download>
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2005-10-29 2:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 0:55 [ANNOUNCE][RFC] PlugSched-6.1.3 for 2.6.13 and 2.6.14-rc4 Peter Williams
2005-10-29 2:35 ` Peter Williams [this message]
2005-11-07 22:01 ` Peter Williams
2005-11-11 3:00 ` [PATCH] Staircase v13 for plugsched 6.1.3 Con Kolivas
2005-11-13 1:36 ` Peter Williams
2005-11-11 3:05 ` [PATCH] plugsched - update Kconfig Con Kolivas
2005-11-11 3:11 ` Con Kolivas
2005-11-11 3:17 ` [PATCH] plugsched - update Kconfig-1 Con Kolivas
2005-11-13 1:34 ` Peter Williams
2005-11-13 1:44 ` Con Kolivas
2005-11-13 5:22 ` Peter Williams
2005-11-13 5:37 ` Con Kolivas
2005-11-13 9:10 ` Peter Williams
2005-11-13 9:30 ` Con Kolivas
2005-11-13 22:52 ` 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=4362DFD5.2000709@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