From: Robert Love <rml@tech9.net>
To: grue@lakesweb.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Feedback on preemptible kernel patch
Date: 08 Sep 2001 01:47:43 -0400 [thread overview]
Message-ID: <999928066.903.18.camel@phantasy> (raw)
In-Reply-To: <20010908052256.A3DE9597C5@g-box.vf.shawcable.net>
In-Reply-To: <20010908052256.A3DE9597C5@g-box.vf.shawcable.net>
On Sat, 2001-09-08 at 01:22, grue@lakesweb.com wrote:
> I am running 2.4.10-pre4 with the rml-preempt patch.
> built and rebooted this on my workstation yesterday when I saw the patch
> posted and it's been working great.
_Very_ glad to hear this.
> I'm running it on a dual P3-550 with 256MB ram with CONFIG_SMP and no
> problems whatsoever although it hasn't been worked 'real' hard yet.
> (load no higher than 4) ;)
I am surprised you have no problems with CONFIG_SMP=y &&
CONFIG_PREEMPT=y. Promising.
> Figured I'd give some positive feedback about the patch. If you want,
> Rob, I could run some benchmarks on this against an unpatched kernel, or
> if you have some ideas for me to really stress this thing to see if it
> breaks, let me know.
I would love this. We could use some SMP datapoints badly.
You can run some of the tests made especially for testing latency, like
an audio benchmark. One such test is at
http://www.gardena.net/benno/linux/latencytest-0.42.tar.gz
Obviously a heavily tasked I/O benchmark is useful, I have used dbench
in the past (ftp://samba.org/pub/tridge/dbench/) (try it with 16
processes or so), but I have been told I should use bonnie.
You can time normal things, too. `time make dep clean bzImage' is always
a favorite :)
Under UP, enabling preemption helps all of this (the recent linuxdevices
article on preemption shows a 30x decrease in latency.). Both myself
and Nigel have run dbench with good results for -16. See
http://kpreempt.sourceforge.net/ for some more.
whatever you can... anyhow, thank you for the positive feedback.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-08 5:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 5:22 Feedback on preemptible kernel patch grue
2001-09-08 5:47 ` Robert Love [this message]
2001-09-08 17:33 ` Arjan Filius
2001-09-08 18:22 ` safemode
2001-09-08 20:58 ` [SMP lock BUG?] " Roger Larsson
2001-09-08 22:18 ` Arjan Filius
2001-09-09 14:55 ` george anzinger
2001-09-09 22:25 ` Arjan Filius
2001-09-09 4:40 ` Robert Love
2001-09-09 17:09 ` Robert Love
2001-09-09 21:07 ` Arjan Filius
2001-09-09 21:26 ` Robert Love
2001-09-09 21:23 ` Arjan Filius
2001-09-09 21:37 ` Robert Love
2001-09-10 3:24 ` Daniel Phillips
2001-09-10 3:37 ` Jeremy Zawodny
2001-09-10 5:09 ` Robert Love
2001-09-10 18:25 ` Daniel Phillips
2001-09-10 21:29 ` Arjan Filius
2001-09-13 17:27 ` Robert Love
2001-09-14 7:30 ` george anzinger
2001-09-14 15:01 ` Robert Love
2001-09-11 19:47 ` Arjan Filius
2001-09-09 18:57 ` grue
2001-09-09 21:44 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-09-11 22:53 Robert Love
2001-09-14 2:47 Dieter Nützel
[not found] <200109140302.f8E32LG13400@zero.tech9.net>
2001-09-14 4:35 ` Robert Love
2001-09-15 4:25 ` Dieter Nützel
[not found] ` <200109150444.f8F4iEG19063@zero.tech9.net>
2001-09-15 5:14 ` Robert Love
2001-09-18 4:06 ` Dieter Nützel
2001-09-18 8:35 ` Daniel Phillips
2001-09-18 18:18 ` Roger Larsson
2001-09-18 23:31 ` Robert Love
2001-09-20 6:40 ` Dieter Nützel
[not found] ` <200109180406.f8I46LG02238@zero.tech9.net>
2001-09-18 23:31 ` Robert Love
[not found] <Pine.LNX.4.33.0109140838040.21992-100000@sjoerd.sjoerdnet>
2001-09-14 15:04 ` Robert Love
2001-09-15 9:44 ` Arjan Filius
2001-09-15 10:38 ` Erik Mouw
2001-09-15 17:57 ` Robert Love
2001-09-15 19:18 Robert Love
2001-09-16 1:28 ` Daniel Phillips
2001-09-16 1:54 ` 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=999928066.903.18.camel@phantasy \
--to=rml@tech9.net \
--cc=grue@lakesweb.com \
--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