From: Robert Love <rml@ufl.edu>
To: safemode <safemode@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-ac10-preempt lmbench output.
Date: 09 Oct 2001 22:02:36 -0400 [thread overview]
Message-ID: <1002679359.862.24.camel@phantasy> (raw)
In-Reply-To: <200110100036.UAA128640@ufl.edu>
In-Reply-To: <200110100036.UAA128640@ufl.edu>
On Tue, 2001-10-09 at 20:36, safemode wrote:
> I'm very pleased so far with ac10 with the preempt patch. Much better than
> 2.4.9-ac18-preempt, which is what i was using. I'm just going to put up some
> output from lmbench to see if anyone who is running the non-preempt version
> is seeing better or worse timings and scores. Perhaps the improvement is
> all in my head due to me moving my atapi devices off of the promise card
> (since you're not supposed to put any on it) and now everything is generally
> running faster despite the kernel being used. Heh. so here they are
I've noticed good improvements on 2.4.10-ac10, too. You may want to try
Rik's eatcache patch available at
http://www.surriel.com/patches/2.4/2.4.10-ac9-eatcache - It does a
noticeable job of preventing the cache thrashing that occurs during
heavy cache activity. This will result in less VM activity, hopefully,
and thus less lock held time. He can use the feedback to tune it
better.
Also, you will really want to run lmbench on 2.4.10-ac10-nopreempt
yourself. While a lot of lmbench is pretty kernel-specific
machine-agnostic, a faster MHz CPU will certainly change almost every
result.
Robert Love
next parent reply other threads:[~2001-10-10 2:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200110100036.UAA128640@ufl.edu>
2001-10-10 2:02 ` Robert Love [this message]
[not found] <200110100358.NAA17519@isis.its.uow.edu.au>
2001-10-10 5:13 ` 2.4.10-ac10-preempt lmbench output Andrew Morton
2001-10-10 5:26 ` Andrea Arcangeli
2001-10-10 11:41 ` safemode
2001-10-10 12:00 ` safemode
[not found] ` <20011010120009.851921E7C9@Cantor.suse.de>
2001-10-10 13:36 ` Andrea Arcangeli
2001-10-10 15:37 ` Dieter Nützel
2001-10-10 20:10 ` Justin A
2001-10-10 23:42 ` safemode
2001-10-11 0:30 ` Mike Fedyk
2001-10-10 18:14 ` george anzinger
[not found] <20011010035818.A556B1E760@Cantor.suse.de>
2001-10-10 4:23 ` Andrea Arcangeli
2001-10-10 4:42 ` Dieter Nützel
[not found] ` <20011010044242.82D131E768@Cantor.suse.de>
2001-10-10 4:48 ` Andrea Arcangeli
[not found] <200110100358.f9A3wSB17421@zero.tech9.net>
2001-10-10 4:02 ` Robert Love
2001-10-10 4:04 ` Robert Love
2001-10-10 4:27 ` Andrea Arcangeli
2001-10-10 3:57 Dieter Nützel
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 0:36 safemode
2001-10-10 1:18 ` Andrea Arcangeli
2001-10-10 2:09 ` safemode
2001-10-10 2:10 ` Robert Love
2001-10-10 2:51 ` Andrea Arcangeli
[not found] ` <20011010020935.50DEF1E756@Cantor.suse.de>
2001-10-10 2:30 ` Andrea Arcangeli
2001-10-10 2:37 ` Robert Love
2001-10-10 3:06 ` Andrea Arcangeli
2001-10-10 3:24 ` Robert Love
2001-10-10 4:03 ` Andrea Arcangeli
2001-10-12 13:22 ` Pavel Machek
2001-10-13 20:42 ` Mike Fedyk
2001-10-13 23:21 ` Robert Love
2001-10-14 6:18 ` Pavel Machek
2001-10-10 5:25 ` Justin A
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=1002679359.862.24.camel@phantasy \
--to=rml@ufl.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@speakeasy.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