From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Nick's scheduler v18
Date: Tue, 11 Nov 2003 04:20:06 +1100 [thread overview]
Message-ID: <3FAFC8C6.8010709@cyberone.com.au> (raw)
http://www.kerneltrap.org/~npiggin/v18/
Nothing exciting for desktop users. High end performance is now starting
to get better.
Has an (unimportant) accounting fix that shouldn't really be here, but
doesn't look like it will get in before 2.6.0.
Average of 5 kernel compiles (make -j) on a 16-way 512KB cache NUMAQ gives
bk14 bk14-v18
real 83.5s 81.7s
user 987.6s 992.5s
sys 158.0s 142.3s
Volanomark looks much better than mainline.
More testing welcome.
next reply other threads:[~2003-11-10 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 17:20 Nick Piggin [this message]
2003-11-13 18:07 ` Nick's scheduler v18 Mary Edie Meredith
2003-11-13 19:39 ` Andrew Morton
2003-11-13 22:27 ` Mike Fedyk
2003-11-14 10:34 ` Sven Luther
2003-11-14 5:45 ` Nick Piggin
2003-11-13 21:30 ` Martin J. Bligh
2003-11-14 2:12 ` Nick Piggin
[not found] <1068589319.1557.1.camel@localhost.localdomain>
2003-11-11 22:30 ` Tom Sightler
2003-11-12 0:38 ` Nick Piggin
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=3FAFC8C6.8010709@cyberone.com.au \
--to=piggin@cyberone.com.au \
--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;
as well as URLs for NNTP newsgroup(s).