From: Con Kolivas <kernel@kolivas.org>
To: linux <linux-kernel@vger.kernel.org>
Cc: Peter Williams <pwil3058@bigpond.net.au>
Subject: [PATCH] Plugsched for 2.6.10-rc1-mm3
Date: Sun, 07 Nov 2004 16:45:33 +1100 [thread overview]
Message-ID: <418DB67D.2000903@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
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.
Cheers,
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2004-11-07 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 5:45 Con Kolivas [this message]
2004-11-08 22:01 ` [PATCH] Plugsched for 2.6.10-rc1-mm3 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=418DB67D.2000903@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pwil3058@bigpond.net.au \
/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