From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Robert Love <rml@tech9.net>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] update: preemptive kernel for O(1) sched
Date: Mon, 14 Jan 2002 01:07:52 +0100 [thread overview]
Message-ID: <20020114000911Z288360-13996+5191@vger.kernel.org> (raw)
In-Reply-To: <200201132325.g0DNPrm05503@zero.tech9.net> <1010965697.813.25.camel@phantasy>
In-Reply-To: <1010965697.813.25.camel@phantasy>
On Monday, 14. January 2002 00:48, you wrote:
> 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.
I'll say that I am running this altogether.
Only vm-22 or rmap-11 are missing for now.
2.4.17 was running for me with vm-21 and preempt+look-beak.
> > 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.
AA, too . Best throughput I've ever seen.
> 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.
But I've only used the VM parts not RCU, etc.
> > What about latencytest0.42-png for latency testing?
>
> A good test.
Expect some numbers (latency) for O(1) with and without preempt+lock-break
maybe with AA-VM, soon.
-Dieter
next prev parent reply other threads:[~2002-01-14 0:09 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
2002-01-14 0:07 ` Dieter Nützel [this message]
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=20020114000911Z288360-13996+5191@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--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®