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.5 for 2.6.14, 2.6.15-rc2 and 2.6.15-rc2-mm1
Date: Mon, 05 Dec 2005 09:37:20 +1100 [thread overview]
Message-ID: <43936FA0.4040409@bigpond.net.au> (raw)
In-Reply-To: <438F7F2E.3080300@bigpond.net.au>
Peter Williams wrote:
> Peter Williams wrote:
>
>> Peter Williams wrote:
>>
>>> This version has a modified (hopefully improved) configuration
>>> mechanism.
>>>
>>> A patch for 2.6.15-rc2-mm1 is available at:
>>>
>>> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.5-for-2.6.15-rc2-mm1.patch?download>
>>>
>>>
>>> and a patch to upgrade the 6.1.4 versions for 2.6.14 and 2.6.15-rc2
>>> to 6.1.5 is available at:
>>>
>>> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.4-to-6.1.5-for-2.6.15-rc2.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
>>
>>
>>
>> Patches for 2.6.15-rc3 available at:
>>
>> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.5-for-2.6.15-rc3.patch?download>
>
>
>
> This patch will also successfully apply to 2.6.15-rc4.
And 2.6.15-rc5.
>
>>
>>
>> and 2.6.15-rc3-mm1 at:
>>
>> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.1.5-for-2.6.15-rc3-mm1.patch?download>
>>
>>
>
>
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
prev parent reply other threads:[~2005-12-04 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 23:12 [ANNOUNCE][RFC] PlugSched-6.1.5 for 2.6.14, 2.6.15-rc2 and 2.6.15-rc2-mm1 Peter Williams
2005-12-01 5:39 ` Peter Williams
2005-12-01 22:54 ` Peter Williams
2005-12-01 23:11 ` Michal Piotrowski
2005-12-04 22:37 ` Peter Williams [this message]
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=43936FA0.4040409@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.