From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Nick's scheduler policy v15a
Date: Mon, 22 Sep 2003 15:40:52 +1000 [thread overview]
Message-ID: <3F6E8B64.2000905@cyberone.com.au> (raw)
In-Reply-To: <3F608807.9090705@cyberone.com.au>
http://www.kerneltrap.org/~npiggin/v15a/
No changes apart from a sync with Linus' tree now that it includes Con's
stuff. It basically just reverts the patches that have gone in. I'm not
sure what the right way to do this would be, but it seems cleaner than to
wade through the remains of my patches after a brute force merge.
This still has known SMP regressions that I haven't got around to looking
at yet because there has been a bit of trouble with a big box I'm supposed
to get time on.
I am still not aware of any desktop / interactivity problems so tell me if
you find any.
prev parent reply other threads:[~2003-09-22 5:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 14:34 Nick's scheduler policy v15 Nick Piggin
2003-09-11 23:29 ` Cliff White
2003-09-12 4:43 ` Mike Fedyk
2003-09-12 18:05 ` Bill Davidsen
2003-09-12 18:39 ` Cliff White
2003-09-13 2:06 ` Nick Piggin
2003-09-13 11:17 ` Nick Piggin
2003-09-14 6:25 ` Cliff White
2003-09-22 5:40 ` Nick Piggin [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=3F6E8B64.2000905@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