From: Ingo Molnar <mingo@elte.hu>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
tglx@linutronix.de, a.p.zijlstra@chello.nl, efault@gmx.de,
acme@redhat.com, fweisbec@gmail.com
Subject: Re: [RFC][PATCH 7/7] Adding general performance benchmarking subsystem to perf.
Date: Tue, 3 Nov 2009 18:24:07 +0100 [thread overview]
Message-ID: <20091103172407.GA11535@elte.hu> (raw)
In-Reply-To: <20091103.195335.229420428319821713.mitake@dcl.info.waseda.ac.jp>
* Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> wrote:
> > There will be a handful of more details i'm sure but once there's a
> > good base we can commit it - would you / will you be interested in
> > extending it further and adding more benchmark modules as well?
> >
> > There's quite a few useful small benchmarks that people are using to
> > measure the kernel. Having a good collection of them in one place,
> > with standardized options and standardized output would be very
> > useful.
>
> Yes, of course! Unified benchmarking utilities will be big help for
> Linux users including me.
>
> e.g. I think that copybench (http://code.google.com/p/copybench/) will
> be good benchmark for I/O, memory and file system. I'll work on this
> after that the patch series I'll send later is merged.
copybench is listed as 'new BSD license'. Might need the pinging of its
author whether he considers it GPLv2 compatible.
> Do you know any other good candidates to include?
Frederic suggested dbench - although that's quite large as it includes a
complete trace of a benchmark run.
We might want to do similar measurements to lmbench.
One nice thing would be to have a 'system call benchmark' set - one that
measures _all_ system calls, and could thus be used to find regressions
on a 'broad' basis. Syscall usage could be gleaned from the LTP project.
Ingo
next prev parent reply other threads:[~2009-11-03 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 4:39 [RFC][PATCH 7/7] Adding general performance benchmarking subsystem to perf Hitoshi Mitake
2009-11-03 7:46 ` Ingo Molnar
2009-11-03 10:53 ` Hitoshi Mitake
2009-11-03 17:24 ` Ingo Molnar [this message]
2009-11-04 10:33 ` Hitoshi Mitake
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=20091103172407.GA11535@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
/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