From: Peter Williams <pwil3058@bigpond.net.au>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Han <xiphux@gmail.com>, Con Kolivas <kernel@kolivas.org>,
William Lee Irwin III <wli@holomorphy.com>,
Jake Moilanen <moilanen@austin.ibm.com>,
Paolo Ornati <ornati@fastwebnet.it>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.3.1 for 2.6.16-rc5
Date: Sun, 02 Apr 2006 12:04:06 +1000 [thread overview]
Message-ID: <442F3116.6070202@bigpond.net.au> (raw)
In-Reply-To: <440508C9.6030701@bigpond.net.au>
Peter Williams wrote:
> Peter Williams wrote:
>> This version updates staircase scheduler to version 14.1 (thanks Con)
>> and includes the latest smpnice patches
>>
>> A patch for 2.6.16-rc5 is available at:
>>
>> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.3.1-for-2.6.16-rc5.patch?download>
>>
>
> and for 2.6.16-rc5-mm1 at:
>
> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.3.1-for-2.6.16-rc5-mm1.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,
>> ingo_ll, nicksched, staircase, spa_no_frills, spa_ws, spa_svr, spa_ebs
>> 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
>
>
Now available for 2.6.16 at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-6.3.1-for-2.6.16.patch?download>
and 2.6.16-mm2 at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-6.3.1-for-2.6.16-mm2.patch?download>
Con and Nick,
I've taken the liberty of modifying staircase and nicksched (in the
2.6.16-mm2 version) to support priority inheritance. I'd appreciate it
if you could review the code?
Thanks,
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-04-02 2:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 22:32 [ANNOUNCE][RFC] PlugSched-6.3.1 for 2.6.16-rc5 Peter Williams
2006-03-01 2:36 ` Peter Williams
2006-04-02 2:04 ` Peter Williams [this message]
2006-04-02 6:02 ` Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 11:59 Al Boldi
2006-04-03 12:13 ` Paolo Ornati
2006-04-03 23:04 ` Peter Williams
2006-04-03 23:29 ` Con Kolivas
2006-04-04 0:01 ` Peter Williams
2006-04-04 0:12 ` Con Kolivas
2006-04-04 1:29 ` Peter Williams
2006-04-04 13:27 ` Al Boldi
2006-04-04 13:27 ` Al Boldi
2006-04-04 23:17 ` Peter Williams
2006-04-05 8:16 ` Al Boldi
2006-04-05 22:53 ` Peter Williams
2006-04-07 21:32 ` Al Boldi
2006-04-08 1:29 ` Peter Williams
2006-04-08 20:31 ` Al Boldi
2006-04-09 2:58 ` Peter Williams
2006-04-09 5:04 ` Al Boldi
2006-04-09 23:53 ` Peter Williams
2006-04-10 14:43 ` Al Boldi
2006-04-11 2:07 ` Peter Williams
2006-04-03 23:27 ` Peter Williams
2006-04-04 13:27 ` Al Boldi
2006-04-04 23:20 ` Peter Williams
2006-04-05 8:16 ` Al Boldi
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=442F3116.6070202@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=moilanen@austin.ibm.com \
--cc=ornati@fastwebnet.it \
--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.