From: Peter Williams <pwil3058@bigpond.net.au>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.4 for 2.6.18-rc2
Date: Tue, 25 Jul 2006 12:44:38 +1000 [thread overview]
Message-ID: <44C58596.8060005@bigpond.net.au> (raw)
In-Reply-To: <200607241857.52389.a1426z@gawab.com>
Al Boldi wrote:
> Peter Williams wrote:
>> This version removes the hard/soft CPU rate caps from the SPA schedulers.
>>
>> A patch for 2.6.18-rc2 is available at:
>>
>> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.4-for-2.6.18-rc2.pat
>> ch?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>
>
> Any reason dynsched couldn't be merged with plugsched?
None that I know of (but I'm not familiar with dynsched). Patches to
add it to the mix would be accepted and once in I would try to keep it
in step with kernel changes.
>
>> 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
>
> It may be really great, to allow schedulers perPid parent, thus allowing the
> stacking of different scheduler semantics. This could aid flexibility a
> lot.
I'm don't understand what you mean here. Could you elaborate?
>
> Worth a try, and should be easy to implement.
>
>> Control parameters for the scheduler can be read/set via files in:
>>
>> /sys/cpusched/<scheduler>/
>
> Thanks for the most important out-of-tree patch that makes 2.6 reasonable.
My pleasure,
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-07-25 2:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 15:57 [ANNOUNCE][RFC] PlugSched-6.4 for 2.6.18-rc2 Al Boldi
2006-07-25 2:44 ` Peter Williams [this message]
2006-07-25 4:57 ` Al Boldi
2006-07-25 5:44 ` Peter Williams
2006-07-25 18:27 ` Al Boldi
2006-07-25 19:40 ` Valdis.Kletnieks
2006-07-26 4:45 ` Al Boldi
2006-07-26 11:28 ` Valdis.Kletnieks
2006-07-26 0:51 ` Peter Williams
2006-07-26 4:45 ` Al Boldi
2006-07-26 5:14 ` Peter Williams
2006-07-26 11:23 ` Al Boldi
2006-07-26 12:34 ` Valdis.Kletnieks
2006-07-26 14:04 ` Al Boldi
2006-07-27 1:32 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2006-07-21 3:24 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=44C58596.8060005@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
/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).