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: Linux Preemptive patch success 2.4.10-pre4 + lots of other
Date: 08 Sep 2001 02:39:51 -0400 [thread overview]
Message-ID: <999931193.838.25.camel@phantasy> (raw)
In-Reply-To: <200109080629.f886TrG13025@zero.tech9.net>
In-Reply-To: <200109080629.f886TrG13025@zero.tech9.net>
On Sat, 2001-09-08 at 02:29, Dieter Nützel wrote:
> I've tested your former patch against 2.4.7-acX and sent you some feedback
> but you didn't answered my post.
>
> Is the module problem (missing preempt_xxx symbols) thing fixed?
I am not sure what module problem you are talking about. There was a
bug in my original patch that caused a link error in most situations
where CONFIG_MODULE was set, but this had to do with
atomic_dec_and_lock, not preempt_xxx -- what preempt_xxx symbols?
Anyhow, I suggest you grab 2.4.9-ac10 and
http://tech9.net/rml/linux/patch-rml-2.4.9-ac10-preempt-kernel-1 and
enable CONFIG_PREEMPT and give that a whirl. You should have no
problems on a UP system.
> Aside from that I saw some nice speed increase (UP Athlon) and very snappy
> system.
Very glad. Especially to hear there are no problems on Athlon.
> dbench-1.1 32 clients load drops to mostly below 16 (33 before)
Great. Data points such as this are welcome. What about the actual
throughput? Both I and Nigel (see http://kpreempt.sourceforge.net)
benched the patch with `dbench -16' and we both got decent throughput
increase.
> Go on with your great work!
Thanks.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next parent reply other threads:[~2001-09-08 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200109080629.f886TrG13025@zero.tech9.net>
2001-09-08 6:39 ` Robert Love [this message]
2001-09-08 6:29 Linux Preemptive patch success 2.4.10-pre4 + lots of other Dieter Nützel
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=999931193.838.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