From: Ingo Molnar <mingo@redhat.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Robert Love <rml@tech9.net>, Andrew Morton <akpm@zip.com.au>,
Andrea Arcangeli <andrea@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCHSET] Linux 2.4.19-pre7-jam1
Date: Fri, 19 Apr 2002 03:43:38 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0204190340450.20646-100000@devserv.devel.redhat.com> (raw)
In-Reply-To: <200204190136.15978.Dieter.Nuetzel@hamburg.de>
On Fri, 19 Apr 2002, Dieter [iso-8859-15] Nützel wrote:
> No uptodate O(1) patch for 2.4. Very sad. So there isn't any change to
> see a current preemption patch on top of vm33 and O(1).
>
> [...]
> I'm under the impression that "all" development is focused on 2.5.x, now.
well, 2.5's scheduler bits were pretty much in flux in the past two months
or so, partly due to the preemption feature going in. And there are a
number of other changes in the pipeline as well. So what makes sense for
2.4 is Robert's plan: to backport O(1)+preempt once 2.5 is slowing down,
that way we get the proper testing of both components, instead of a
separated scheduler patch that doesnt even exist in that form in 2.5.
Ingo
next prev parent reply other threads:[~2002-04-19 7:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 23:36 Dieter Nützel
2002-04-18 23:44 ` Robert Love
2002-04-19 0:04 ` Dieter Nützel
2002-04-19 7:43 ` Ingo Molnar [this message]
2002-04-19 11:19 ` Dieter Nützel
-- strict thread matches above, loose matches on Subject: below --
2002-04-17 0:03 J.A. Magallon
2002-04-17 0:21 ` Andre Hedrick
2002-04-17 13:40 ` J.A. Magallon
2002-04-17 17:23 ` Andre Hedrick
2002-04-18 8:11 ` Heinz Diehl
2002-04-18 19:27 ` J.A. Magallon
2002-04-18 19:34 ` Andre Hedrick
2002-04-18 19:53 ` Erik Andersen
2002-04-18 20:16 ` Andre Hedrick
2002-04-19 5:52 ` Jens Axboe
2002-04-19 14:05 ` Heinz Diehl
2002-04-19 20:30 ` Andre Hedrick
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=Pine.LNX.4.44.0204190340450.20646-100000@devserv.devel.redhat.com \
--to=mingo@redhat.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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
all inboxes | Powered by JetHome®