From: William Lee Irwin III <wli@holomorphy.com>
To: Robert Love <rml@tech9.net>
Cc: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] update: preemptive kernel for O(1) sched
Date: Sun, 13 Jan 2002 17:32:22 -0800 [thread overview]
Message-ID: <20020113173222.D934@holomorphy.com> (raw)
In-Reply-To: <200201132325.g0DNPrm05503@zero.tech9.net> <1010965697.813.25.camel@phantasy>
In-Reply-To: <1010965697.813.25.camel@phantasy>; from rml@tech9.net on Sun, Jan 13, 2002 at 06:48:17PM -0500
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 ...;-)
On Sun, Jan 13, 2002 at 06:48:17PM -0500, Robert Love wrote:
> 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 have at least run it on my laptop, together with rmap even.
No pathological behavior that I can tell. Of course, the interactive
response is wonderful, but I haven't precisely measured anything, as
I have enough other things to measure precisely it's a bit far afield.
Cheers,
Bill
next prev parent reply other threads:[~2002-01-14 1:33 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 ` [PATCH] update: preemptive kernel for O(1) sched Robert Love
2002-01-14 0:07 ` Dieter Nützel
2002-01-14 1:32 ` William Lee Irwin III [this message]
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=20020113173222.D934@holomorphy.com \
--to=wli@holomorphy.com \
--cc=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