public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@innominate.de>
To: ludovic fernandez <ludovic.fernandez@sun.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.0-prerelease: preemptive kernel.
Date: Fri, 05 Jan 2001 01:56:55 +0100	[thread overview]
Message-ID: <3A551BD7.E8708B6F@innominate.de> (raw)
In-Reply-To: <Pine.LNX.4.05.10101041157540.4778-100000@cosmic.nrg.org> <3A54DEBF.794C2E6A@sun.com>

ludovic fernandez wrote:
> Right now I will be interested to run some benchmarks (latency but
> also performance) to see how the system is disturbed by beeing
> preemptable. I'm little bit lost on this and I don't know where to start.
> Do you have any pointers on benchmark suites I could run ?
> Also, maybe it's a off topic subject now....

No!  Not off topic.  And I hope you don't throw away that simple patch,
it will always be useful for doing reality checks on the performance of
the fancy system, and who knows, maybe it's useful in its own right.

The current fashion is to use dbench:

  ftp://samba.org/pub/tridge/dbench

I think this is good for your patch because it's inherently parallel. 
Interesting numbers of tasks are, e.g., 1, 2, 10, 50.   Of course dbench
is not the last word in benchmarks but it's been pretty useful so far. 
You probably want something entirely cpu-bound too.  How about dbench
with ramfs?

--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-05  1:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04  1:56 [PATCH] 2.4.0-prerelease: preemptive kernel ludovic fernandez
2001-01-04  7:35 ` Daniel Phillips
2001-01-04  8:11   ` Andi Kleen
2001-01-04 12:32     ` Anton Blanchard
2001-01-04 12:44       ` Andi Kleen
2001-01-04 21:54         ` Nigel Gamble
2001-01-04 21:39     ` Nigel Gamble
2001-01-04 22:09       ` Andi Kleen
2001-01-04 22:28         ` Nigel Gamble
2001-01-04  8:43   ` ludovic fernandez
2001-01-04 22:10     ` Roger Larsson
2001-01-04 23:16       ` ludovic fernandez
2001-01-05  0:10         ` Nigel Gamble
2001-01-05  0:36           ` ludovic fernandez
2001-01-05  0:45             ` Andi Kleen
2001-01-05  1:13               ` Alan Olsen
2001-01-05  5:29       ` george anzinger
2001-01-05  6:45         ` ludovic fernandez
2001-01-05  8:10           ` george anzinger
2001-01-04 21:28   ` Nigel Gamble
2001-01-04  9:00 ` David Woodhouse
2001-01-04 16:17 ` Rik van Riel
2001-01-04 20:06 ` Nigel Gamble
2001-01-04 20:36   ` ludovic fernandez
2001-01-05  0:56     ` Daniel Phillips [this message]

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=3A551BD7.E8708B6F@innominate.de \
    --to=phillips@innominate.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.fernandez@sun.com \
    /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