mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.5.1 for  2.6.22
Date: Thu, 12 Jul 2007 01:17:20 +0300	[thread overview]
Message-ID: <200707120117.20405.a1426z@gawab.com> (raw)

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.

> 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?


Thanks!

--
Al


             reply	other threads:[~2007-07-11 22:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 22:17 Al Boldi [this message]
2007-07-15  4:19 ` Giuseppe Bilotta
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=200707120117.20405.a1426z@gawab.com \
    --to=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

all inboxes | Powered by JetHome®