public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Benchmarks for performance patches (-ck) for 2.4.19
Date: Mon,  2 Sep 2002 13:42:36 +1000	[thread overview]
Message-ID: <1030938156.3d72de2c231ac@kolivas.net> (raw)
In-Reply-To: <200209020524.41937.Dieter.Nuetzel@hamburg.de>

Quoting Dieter Nützel <Dieter.Nuetzel@hamburg.de>:

> I have your ck5_2.4.19.patch with some additional stuff running fine on my 
> dual Athlon MP 1900+, MSI K7D Master-L, 1 GB DDR-SDRAM 266 CL.

Great to hear. I'd be impressed if you noticed *any* change in responsiveness
with anything on that machine.

> ck5 + some 2.4.19-jam0 stuff (Andrea, Ingo, others)
> 
> 000_e100-2.1.6 (-AA)
> 000_e1000-4.3.2 (-AA)
> 00_387-fix-1
> 10-module-size-checks
> 12-memparam
> 24-config-nr_cpus
> 30-smptimers-A0
> 30_irq-balance-12
> 31-nr_requests
> 70-i2c-2.6.4
> 71-sensors-2.6.4
> 
> 2.4.19.pending ReiserFS stuff
> linux-2.4.19-ntfs-2.1.0a.patch
> page_color-2.4.19-pre10-1 (Page coloring)
> 
> I'm from Robert Love's "side" and have his stuff running on top of 2.4 for 
> nearly one year, now.
> 
> The first bench I try is latencytest-0.42-png all the time.
> http://www.gardena.net/benno/linux/audio/

That's a very nice test, but as you've seen, pure latency is not everything. If
you want just that you should try my ck5-ll patch which gives the lowest
latencies (check my website for the benchmarks on -ck4 which used this -ll branch).

> Then I try dbench (Yes, I know Rik ;-) to see the GREAT speed of Andrea 
> Arcangeli's -AA VM which improve noticeably with the Preemption patch.
> O(1) gave some additional speed, too.

Yes, dbench is included in the many tests available at the the Open Source
Development Lab (osdl.org) along with many others.

> What about Robert's nice Preemption Latency Measurement Tool?
> http://www.tech9.net/rml/linux

Once again a pure latency measure, no?

> I tried it many times to gave Robert some feedback.
> 
> Regards and good work!

Thanks, glad you enjoy it, but it's really the combined efforts of the real
developers as you know.

Thanks for your feedback
Con

  parent reply	other threads:[~2002-09-02  3:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  3:24 Benchmarks for performance patches (-ck) for 2.4.19 Dieter Nützel
2002-09-02  3:41 ` Rik van Riel
2002-09-02  3:42 ` Con Kolivas [this message]
2002-09-02  4:21   ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2002-09-04  5:15 Wade
2002-09-02 12:50 Martin Knoblauch
2002-09-02  9:12 Con Kolivas
2002-09-04  3:39 ` Paul
2002-09-02  1:10 Con Kolivas
2002-09-02  2:03 ` Ed Sweetman
2002-09-02  2:32   ` Rik van Riel
2002-09-02  4:00     ` Ed Sweetman
2002-09-02  7:39       ` Ingo Oeser
2002-09-02 13:20         ` Rik van Riel
2002-09-03  3:16         ` jw schultz
2002-09-02  5:22     ` Paul
2002-09-02  5:40       ` J Sloan
2002-09-02  5:57       ` Andrew Morton

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=1030938156.3d72de2c231ac@kolivas.net \
    --to=conman@kolivas.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