[PATCH 0/4][RFC] perf bench: prepare framework for parallel oriented benchmarking

[Hitoshi Mitake]

Hi Ingo,

I made a change on "perf bench" and made patch series
for parallel oriented benchmarking.

Previous perf bench provided only least
framework for each benchmark programs,
but I felt this was not enough.

Because it seems that lots of today's performance issue
is found by multi thread/process programs.

So I made perf bench to provide the framework
for easy parallel benchmark writing.

And this is a preparation for "perf bench syscall".
Because each benchmarks of system call
will be required parallel workloads,
but parallel frameworks for each benchmarks will be fat code.

Request for comments!

Cc: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
Cc: Paul Mackerras <paulus@xxxxxxxxx>
Cc: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx>

Hitoshi Mitake (4):
  perf bench: add "sample" subsystem and "sample" suite as sample
    benchmark program
  perf bench: fix "mem" subsystem to adopt new style of perf bench
  perf bench: fix "sched" subsystem to adopt new style of perf bench
  perf bench: improve perf bench for parallel oriented benchmarking

 tools/perf/Makefile                |    5 +
 tools/perf/bench/bench.h           |   32 ++
 tools/perf/bench/mem-memcpy.c      |  182 ++++--------
 tools/perf/bench/mem.h             |    4 +
 tools/perf/bench/sample-sample.c   |   98 +++++++
 tools/perf/bench/sample.h          |    4 +
 tools/perf/bench/sched-messaging.c |  553 ++++++++++++++++++++----------------
 tools/perf/bench/sched-pipe.c      |  146 +++++-----
 tools/perf/bench/sched.h           |    8 +
 tools/perf/builtin-bench.c         |  227 +++++++++++----
 10 files changed, 762 insertions(+), 497 deletions(-)
 create mode 100644 tools/perf/bench/mem.h
 create mode 100644 tools/perf/bench/sample-sample.c
 create mode 100644 tools/perf/bench/sample.h
 create mode 100644 tools/perf/bench/sched.h

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