From: Tom Rini <trini@kernel.crashing.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OKS] O(1) scheduler in 2.4
Date: Mon, 1 Jul 2002 11:12:28 -0700 [thread overview]
Message-ID: <20020701181228.GF20920@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.3.96.1020701134937.23820A-100000@gatekeeper.tmr.com>
On Mon, Jul 01, 2002 at 01:52:54PM -0400, Bill Davidsen wrote:
> What's the issue?
a) We're at 2.4.19-rc1 right now. It would be horribly
counterproductive to put O(1) in right now.
b) 2.4 is the _stable_ tree. If every big change in 2.5 got back ported
to 2.4, it'd be just like 2.5 :)
c) I also suspect that it hasn't been as widley tested on !x86 as the
stuff currently in 2.4. And again, 2.4 is the stable tree.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-07-01 18:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:52 [OKS] O(1) scheduler in 2.4 Bill Davidsen
2002-07-01 18:12 ` Tom Rini [this message]
2002-07-01 23:44 ` J.A. Magallon
2002-07-02 2:48 ` Tom Rini
2002-07-03 1:11 ` Rob Landley
2002-07-03 7:30 ` Adrian Bunk
2002-07-03 8:35 ` Ingo Molnar
2002-07-04 3:36 ` Bill Davidsen
2002-07-04 6:56 ` Ingo Molnar
2002-07-04 7:36 ` J Sloan
2002-07-05 6:18 ` Andrew Rodland
2002-07-05 6:56 ` Adrian Bunk
2002-07-05 7:02 ` Andrew Rodland
2002-07-05 9:12 ` William Lee Irwin III
2002-07-04 18:08 ` Rob Landley
2002-07-05 11:17 ` Bill Davidsen
2002-07-05 15:09 ` Rob Landley
2002-07-06 4:31 ` Bill Davidsen
2002-07-06 23:10 ` Rob Landley
2002-07-07 10:55 ` Bill Davidsen
2002-07-02 16:05 ` venom
2002-07-02 16:53 ` Tomas Szepe
2002-07-02 14:46 ` Bill Davidsen
2002-07-02 15:12 ` Tom Rini
2002-07-04 4:02 ` Bill Davidsen
2002-07-04 4:17 ` Tom Rini
2002-07-01 18:49 ` Ingo Molnar
2002-07-02 15:07 ` Bill Davidsen
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=20020701181228.GF20920@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=davidsen@tmr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.