public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
	Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Mike Galbraith" <efault@gmx.de>
Subject: Re: [PATCH][RFC] Adding hackbench.c to tools/
Date: Mon, 2 Nov 2009 11:41:24 +0100	[thread overview]
Message-ID: <20091102104124.GA5193@elte.hu> (raw)
In-Reply-To: <20091101.131027.680961629714047921.mitake@dcl.info.waseda.ac.jp>


* Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> wrote:

> Hi Ingo,
> 
> It seems that hackbench is the de-fact standard benchmarking program 
> for scheduler of Linux. But when I ask google where hackbench.c is, 
> some answers are replied. Like these, (in order of google result)
> 
> http://devresources.linux-foundation.org/craiger/hackbench/ (this page 
> containts link to hackbench.c) 
> http://people.redhat.com/mingo/cfs-scheduler/tools/hackbench.c
> 
> And it seems that second one is newer.
> 
> I think this situation is very confusable. So I wrote this patch to 
> add hackbench to tools/ of kernel tree. This may help hackbench users 
> like me.

I think we can do something nicer: would you be interested in adding it 
as a 'perf bench hackbench' sub-command of tools/perf/?

We already have the tools to measure scheduling behavior under 'perf 
sched', so having a 'perf bench' array of common tests would be nice to 
have.

( I've Cc:-ed Rusty, the original author of hackbench.c. Rusty, the file 
  has no explicit GPLv2 compatible license - is it fine to be put
  into GPLv2 code? )

Adding a new perf sub-command is easy:

create a new tools/perf/builtin-bench.c file and copy hackbench.c to it, 
add it to command-list.txt and to the Makefile - add it to perf.c's 
array of built-in commands and [optional] add a 
Documentation/perf-bench.txt file to generate manpages and usage strings 
for it.

Change the 'main' function to cmd_bench() and add option parsing like 
you can see in the other builtin-*.c files. This should get you going.

Eventually we'd add more scheduler (and other) benchmarks too, not just 
hackbench. I'd also suggest to name it not 'hackbench' but something 
more generic, like:

  perf bench sched messaging

So that we can have subsystem identifier first, then the type of 
benchmark.

	Ingo

  reply	other threads:[~2009-11-02 10:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01  4:10 [PATCH][RFC] Adding hackbench.c to tools/ Hitoshi Mitake
2009-11-02 10:41 ` Ingo Molnar [this message]
2009-11-02 13:27   ` Rusty Russell
2009-11-02 13:51     ` [PATCH][RFC] Adding benchmark subsystem to perf Hitoshi Mitake
2009-11-02 14:26       ` Mike Galbraith
2009-11-03  4:26         ` 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=20091102104124.GA5193@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