From: Con Kolivas <kernel@kolivas.org>
To: linux list <linux-kernel@vger.kernel.org>, ck list <ck@vds.kolivas.org>
Subject: [PATCH] Staircase cpu scheduler v15 for 2.6.17-rc1*
Date: Sun, 9 Apr 2006 22:56:52 +1000 [thread overview]
Message-ID: <200604092256.56437.kernel@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Patches for the current staircase cpu scheduler (v15) for 2.6.17-rc1 are here:
http://www.kernel.org/pub/linux/kernel/people/ck/patches/staircase/2.6.17-rc1/2.6.17-rc1-staircase-15.patch
and for mm2 here:
http://www.kernel.org/pub/linux/kernel/people/ck/patches/staircase/2.6.17-rc1/2.6.17-rc1-mm2/2.6.17-rc1-mm2-staircase-15.patch
Martin Bligh was kind enough to put the current version of staircase on
2.6.17-rc1 for testing on http://test.kernel.org/
Performance more or less parallels mainline 2.6.17-rc1 (apart from
interactivity as shown here previously where staircase mostly trumps
mainline).
Jens Axboe was also kind enough to do a kernbench run on 4xIA64 which also
showed no performance difference. See
http://article.gmane.org/gmane.linux.kernel.ck/5472 (the 2nd run is staircase
and the attachments seem to be listed twice by gmane)
Just as a reminder of how much less code than the ever increasing complexity
mainline scheduler staircase is, here is a diffstat of the patch for
2.6.17-rc1-mm2:
fs/proc/array.c | 4
include/linux/sched.h | 20 -
kernel/exit.c | 1
kernel/sched.c | 987
++++++++++++++++----------------------------------
4 files changed, 327 insertions(+), 685 deletions(-)
--
-ck
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2006-04-09 12:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200604092256.56437.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.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.