| From: |
| Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> |
| To: |
| mingo@elte.hu, linux-kernel@vger.kernel.org |
| Subject: |
| [PATCH v5 0/7] Adding general performance benchmarking subcommand to perf. |
| Date: |
| Thu, 5 Nov 2009 09:31:30 +0900 |
| Message-ID: |
| <1257381097-4743-1-git-send-email-mitake@dcl.info.waseda.ac.jp> |
| Cc: |
| Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
Rusty Russell <rusty@rustcorp.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
fweisbec@gmail.com, Jiri Kosina <jkosina@suse.cz> |
| Archive-link: |
| Article, Thread
|
This patch series add general benchmark subcommand to perf.
The subcommand will unify the benchmarking programs
and provide these in standardized way.
I fixed this series for latest tip tree.
My previous patch series conflicts with cmd_probe().
So please discard v4 and use this v5.
Hitoshi Mitake (7):
Adding new directory and header for new subcommand 'bench'
sched-messaging.c: benchmark for scheduler and IPC mechanisms based
on hackbench
sched-pipe.c: benchmark for pipe() system call
builtin-bench.c: General framework for benchmark suites
Modifying builtin.h for new prototype
Modyfing perf.c for subcommand 'bench'
Modyfing Makefile to build subcommand 'bench'
tools/perf/Makefile | 6 +
tools/perf/bench/bench.h | 9 +
tools/perf/bench/sched-messaging.c | 332 ++++++++++++++++++++++++++++++++++++
tools/perf/bench/sched-pipe.c | 113 ++++++++++++
tools/perf/builtin-bench.c | 128 ++++++++++++++
tools/perf/builtin.h | 1 +
tools/perf/perf.c | 1 +
7 files changed, 590 insertions(+), 0 deletions(-)
create mode 100644 tools/perf/bench/bench.h
create mode 100644 tools/perf/bench/sched-messaging.c
create mode 100644 tools/perf/bench/sched-pipe.c
create mode 100644 tools/perf/builtin-bench.c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/