From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Nick's scheduler v17a
Date: Thu, 30 Oct 2003 14:41:07 +1100 [thread overview]
Message-ID: <3FA08853.5050402@cyberone.com.au> (raw)
In-Reply-To: <3F913704.5040707@cyberone.com.au>
http://www.kerneltrap.org/~npiggin/v17a/
More balancing fixes. I also incorporated some of Andrew Theurer's
ideas. I'm generally getting good numbers now, but using fairly
synthetic benchmarks.
Now would be a good time to test if anyone is interested. Thanks.
next prev parent reply other threads:[~2003-10-30 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 12:50 Nick's scheduler v16 Nick Piggin
2003-10-18 13:18 ` Nick Piggin
2003-10-21 21:16 ` Martin J. Bligh
2003-10-22 1:43 ` Nick Piggin
2003-10-22 14:07 ` Nick's scheduler v16 - reaim Cliff White
2003-10-23 2:02 ` Nick Piggin
2003-10-30 3:41 ` Nick Piggin [this message]
2003-10-31 22:57 ` Nick's scheduler v17a Rhino
2003-11-03 4:47 ` 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=3FA08853.5050402@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