From: Robert Love <rml@tech9.net>
To: Brandon Low <lostlogic@gentoo.org>
Cc: 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:18:29 -0400 [thread overview]
Message-ID: <1033665510.743.27.camel@phantasy> (raw)
In-Reply-To: <20021003120329.H6891@lostlogicx.com>
On Thu, 2002-10-03 at 13:03, Brandon Low wrote:
> Unfortunately some of the scheduler bits that have been merged into
> 2.4.20-pre have broken the nice patch that robert has, I'm hoping he can
> re-diff it for us (me) because I like to have the option of getting O(1)
> without using Alan's tree.
I just put a 2.4.19 final patch up. I will do a 2.4.20-pre/2.4.20 patch
eventually but it is not at the top of my list. I would not think
managing the rejects is too difficult.
It is a much higher priority keeping the 2.4-ac and 2.5 scheduler sane.
Robert Love
next prev parent reply other threads:[~2002-10-03 17:13 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 [this message]
2002-10-03 17:17 ` Robert Love
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=1033665510.743.27.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lostlogic@gentoo.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