public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: "J.A. Magallon" <jamagallon@able.es>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@zip.com.au>, Ingo Molnar <mingo@redhat.com>,
	Andrea Arcangeli <andrea@suse.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCHSET] Linux 2.4.19-pre7-jam1
Date: 18 Apr 2002 19:44:41 -0400	[thread overview]
Message-ID: <1019173481.5395.149.camel@phantasy> (raw)
In-Reply-To: <200204190136.15978.Dieter.Nuetzel@hamburg.de>

On Thu, 2002-04-18 at 19:36, Dieter 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 am working on backports of all the O(1) scheduler changes in 2.5, the
pending changes, and some other misc. bits.  I also have versions of the
migration_thread and affinity stuff for 2.4.

I will release a general O(1) patch and a patch for -ac soon - hopefully
tomorrow or Monday.  I have no idea if it fixes the problems you are
seeing, because I have no idea what caused a regression in the O(1)
code.

> No, lowlatency didn't come close to preemption+lock-break (best latency 
> numbers for 2.4.17-preX-rml, were ~2.9ms max).

Good to hear ;)

> I'm under the impression that "all" development is focused on 2.5.x, now.
> Even the VM stuff show no mayor growth ;-(

That is the point of 2.5 :)

Development => !Stability and people need to start using 2.4 to get work
done, not reap faster and faster benchmarks times.  I seriously suspect
2.4 is performing fine right now for what you are doing, anyhow.

Also, a lot of VM work is happening in 2.4 (and not in 2.5 even, at the
moment).  2.4.19-pre has seen a few of the -aa bits merged and should
see most of the others in due time.

There is also Rik's -rmap for 2.4 ...

	Robert Love


  reply	other threads:[~2002-04-18 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 23:36 [PATCHSET] Linux 2.4.19-pre7-jam1 Dieter Nützel
2002-04-18 23:44 ` Robert Love [this message]
2002-04-19  0:04   ` Dieter Nützel
2002-04-19  7:43 ` Ingo Molnar
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=1019173481.5395.149.camel@phantasy \
    --to=rml@tech9.net \
    --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=mingo@redhat.com \
    /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