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.1 for 2.6.13 and 2.6.13-mm2
Date: Tue, 13 Sep 2005 18:15:15 +1000 [thread overview]
Message-ID: <43268A93.9010800@bigpond.net.au> (raw)
In-Reply-To: <4323896F.5050703@bigpond.net.au>
Peter Williams wrote:
> This version contains minor code cleanups and more modifications to the
> spa_ws scheduler to improve its interactive responsiveness. This
> modification includes control parameters for the identification of
> "media streaming" tasks. The default values for these parameters are
> set based on observations of RealPlayer and the parameters of the video
> and audio benchmarks in Con Kolivas's interbench test and, therefore,
> may need adjusting for other programs.
>
> A patch for 2.6.13-mm2 is available at:
>
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.13-mm2.patch?download>
>
>
> and a patch to upgrade the 6.1 for 2.6.13 to 6.1.1 is available at:
>
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1-to-6.1.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
A patch for 2.6.14-rc1 is available at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.1-for-2.6.14-rc1.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-09-13 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 1:33 [ANNOUNCE][RFC] PlugSched-6.1.1 for 2.6.13 and 2.6.13-mm2 Peter Williams
2005-09-11 20:57 ` oops plugsched, spa_ws, scsi, sata, ata_piix, threading 2.6.13-mm2 Michal Piotrowski
2005-09-11 23:09 ` Peter Williams
2005-09-12 0:09 ` Michal Piotrowski
2005-09-13 8:15 ` Peter Williams [this message]
2005-09-23 7:05 ` [ANNOUNCE][RFC] PlugSched-6.1.1 for 2.6.13 and 2.6.13-mm2 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=43268A93.9010800@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;
as well as URLs for NNTP newsgroup(s).