All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: linux <linux-kernel@vger.kernel.org>
Cc: Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH] Plugsched for 2.6.10-rc1-mm3
Date: Tue, 09 Nov 2004 09:01:51 +1100	[thread overview]
Message-ID: <418FECCF.1060609@bigpond.net.au> (raw)
In-Reply-To: <418DB67D.2000903@kolivas.org>

Con Kolivas wrote:
> While mainline seems uninterested in pluggable cpu schedulers, it seems 
> the demand and response off-list has been rather large so I'll continue 
> to develop it.
> 
> http://ck.kolivas.org/patches/plugsched/2.6.10-rc1-mm3/
> 
> has a patch tarball and a rolled up patch for applying the current 
> plugsched infrastructure.
> 
> 
> Changes:
> Rolled up the bugfixes into their respective parent patches.
> Added an optional private set_task_cpu.
> Privatised get_idle for kgdb.
> Privatised normalise rt sysrq.
> Updated staircase cpu scheduler.
> 
> 
> Planned:
> More shared code between schedulers.
> Sysfs tunables.
> 
> 
> Note that mm3 has some vm bugs leading to compile problems and 
> instability that you'd need to add on if you wish to try these patches.

A port of the Zaphod scheduler as a plugsched module for the 0411071616 
version of plugsched for the 2.6.10-rc1-mm3 kernel is available at:

<http://prdownloads.sourceforge.net/cpuse/2.6.10-rc1-mm3-plugsched-0411071616-zaphod-v0.1.diff?download>

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

      reply	other threads:[~2004-11-08 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-07  5:45 [PATCH] Plugsched for 2.6.10-rc1-mm3 Con Kolivas
2004-11-08 22:01 ` 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=418FECCF.1060609@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=kernel@kolivas.org \
    --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 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.