From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.5.1 for 2.6.22
Date: Sun, 15 Jul 2007 06:19:46 +0200 [thread overview]
Message-ID: <f7c78t$lqe$1@sea.gmane.org> (raw)
In-Reply-To: 200707120117.20405.a1426z@gawab.com
On Thursday 12 July 2007 00:17, Al Boldi wrote:
> Peter Williams wrote:
>>
>> Probably the last one now that CFS is in the main line :-(.
>
> What do you mean? A pluggable scheduler framework is indispensible even in
> the presence of CFS or SD.
Indeed, and I hope it gets merged, giving people the chance to test out
different schedulers easily, without having to do patching, de-patching,
re-patching and blah blah blah.
But somehow I doubt it'll get merged now. My bet is that it won't even be
taken into consideration, for the same reasons that ultimately drove Con
Kolivas to giving up on development of SD. And if it's so, chances are
people will get tired of trying to get it merged. :/
>> A patch for 2.6.22 is available at:
>>
>> <http://downloads.sourceforge.net/cpuse/plugsched-6.5.1-for-2.6.22.patch>
>>
>> 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).
>
> Can't PlugSched include CFS and SD?
If I read the announcement correctly, those are the ones referred to as
'ingosched' and 'staircase' :)
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2007-07-15 4:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 22:17 [ANNOUNCE][RFC] PlugSched-6.5.1 for 2.6.22 Al Boldi
2007-07-15 4:19 ` Giuseppe Bilotta [this message]
2007-07-15 17:47 ` Li, Tong N
2007-07-15 23:45 ` Adrian Bunk
2007-07-16 5:03 ` Li, Tong N
2007-07-16 6:56 ` Adrian Bunk
2007-07-16 18:32 ` Siddha, Suresh B
-- strict thread matches above, loose matches on Subject: below --
2007-08-16 20:42 devzero
2007-08-16 21:14 ` Valdis.Kletnieks
2007-07-11 5:44 Peter Williams
2007-07-16 8:20 ` Ingo Molnar
2007-07-17 0:09 ` Peter Williams
2007-07-18 9:46 ` Ingo Molnar
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='f7c78t$lqe$1@sea.gmane.org' \
--to=giuseppe.bilotta@gmail.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