From: Robert Love <rml@tech9.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: O(1) scheduler for 2.4.(19|20-pre.)?
Date: 03 Oct 2002 13:17:27 -0400 [thread overview]
Message-ID: <1033665449.909.24.camel@phantasy> (raw)
In-Reply-To: <1033647544.28022.2.camel@irongate.swansea.linux.org.uk>
On Thu, 2002-10-03 at 08:19, Alan Cox wrote:
> 2.4.19-ac/2.4.20-ac, Red Hat 7.3, Red Hat 8.0, and probably quite a
> few other places. I think Robert had a set of patches versus plain
> 2.4.19 too
Yep, see:
http://www.kernel.org/pub/linux/kernel/people/rml/sched/ingo-O1/
I would recommend using 2.4-ac over mainline with my patches, however.
Alan's tree is well-tested and I send him scheduler fixes quicker than I
update my own patches :)
It has lots of other nice bits, too.
Robert Love
prev parent reply other threads:[~2002-10-03 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 9:48 O(1) scheduler for 2.4.(19|20-pre.)? Roy Sigurd Karlsbakk
2002-10-03 12:19 ` Alan Cox
2002-10-03 17:03 ` Brandon Low
2002-10-03 17:18 ` Robert Love
2002-10-03 17:17 ` Robert Love [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=1033665449.909.24.camel@phantasy \
--to=rml@tech9.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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