From: Robert Love <rml@tech9.net>
To: venom@sns.it
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] O(1) scheduler for 2.4.19-rc1
Date: 02 Jul 2002 15:18:00 -0700 [thread overview]
Message-ID: <1025648280.991.1338.camel@sinai> (raw)
In-Reply-To: <Pine.LNX.4.43.0207030007040.30706-100000@cibs9.sns.it>
On Tue, 2002-07-02 at 15:10, venom@sns.it wrote:
> On 2 Jul 2002, Robert Love wrote:
>
> > As I am the one doing these 2.4 patches, I will invariably be asked
> > whether I intend for the O(1) scheduler to be merged into 2.4. The
> > answer is a strong NO.
>
> Of course, I think you know that you will also asked WHY?
Because I do not think 2.4 should be a breeding ground for every new
feature that wets someone's appetite. It should be stable and trusted
before anything else. We also have to worry about architecture
support. Let the scheduler be 2.5's thing.
> Also if I can immagine your reasons, as similar discussions have been
> done for preemption patch and so on, and as I said at the times, I Agree.
I do not think preemption should go in 2.4, either. It too is a 2.5
thing.
> 2.5 is the place for this new and cool stuff.
Agreed.
Robert Love
prev parent reply other threads:[~2002-07-02 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 17:11 Robert Love
2002-07-02 22:10 ` venom
2002-07-02 22:18 ` 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=1025648280.991.1338.camel@sinai \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=venom@sns.it \
/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
all inboxes | Powered by JetHome®