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: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] update: preemptive kernel for O(1) sched
Date: 13 Jan 2002 18:48:17 -0500	[thread overview]
Message-ID: <1010965697.813.25.camel@phantasy> (raw)
In-Reply-To: <200201132325.g0DNPrm05503@zero.tech9.net>
In-Reply-To: <200201132325.g0DNPrm05503@zero.tech9.net>

On Sun, 2002-01-13 at 18:22, Dieter Nützel wrote:

> what about lock-break?
> I am running your former one as always with 
> lock-break-rml-2.4.18-pre1-1.patch ...;-)

I haven't tested O(1) together with lock-break personally, yet, but I
have a confirmation of success from a couple of users.  There are no
reasons it shouldn't work.

> Any success together with AA vm-22?

Again I don't have any personal tests.  I do know, however, the Rik's
rmap VM works great.

I suspect Andrea's updated VM from -aa will work, but there may be other
parts of his patch (RCU) that are not preempt friendly.

> What about latencytest0.42-png for latency testing?

A good test.

	Robert Love


       reply	other threads:[~2002-01-13 23:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200201132325.g0DNPrm05503@zero.tech9.net>
2002-01-13 23:48 ` Robert Love [this message]
2002-01-14  0:07   ` [PATCH] update: preemptive kernel for O(1) sched Dieter Nützel
2002-01-14  1:32   ` William Lee Irwin III
2002-01-15 19:48     ` Robert Love
2002-01-13 23:22 Dieter Nützel
  -- strict thread matches above, loose matches on Subject: below --
2002-01-13 22:31 Robert Love
2002-01-14  4:34 ` Robert Love
2002-01-15 14:58   ` Daniel Phillips
2002-01-15 14:58   ` Daniel Phillips
2002-01-15 14:58   ` Daniel Phillips

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=1010965697.813.25.camel@phantasy \
    --to=rml@tech9.net \
    --cc=Dieter.Nuetzel@hamburg.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox