[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1445241870-24854-1-git-send-email-mingo@kernel.org>
Date: Mon, 19 Oct 2015 10:04:16 +0200
From: Ingo Molnar <mingo@...nel.org>
To: linux-kernel@...r.kernel.org
Cc: Peter Zijlstra <peterz@...radead.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...hat.com>
Subject: [PATCH 00/14] perf bench: Misc improvements
So I'm working towards adding more 'perf bench' benchmarks and found
a few rough edges - fixed by the series below.
Thanks,
Ingo
Ingo Molnar (14):
perf/bench: Improve the 'perf bench mem memcpy' code readability
perf/bench: Default to all routines in 'perf bench mem'
perf/bench: Eliminate unused argument from bench_mem_common()
perf/bench: Rename 'mem-memcpy.c' => 'mem-functions.c'
perf/bench: Remove the prefaulting complication from 'perf bench mem mem*'
perf/bench: List output formatting options on 'perf bench -h'
perf/bench/mem: Change 'cycle' to 'cycles'
perf/bench/mem: Rename 'routine' to 'routine_str'
perf/bench/mem: Fix 'length' vs. 'size' naming confusion
perf/bench/mem: Improve user visible strings
perf/bench/mem: Reorganize the code a bit
perf/bench: Harmonize all the -l/--nr_loops options
perf/bench/mem: Rename 'routine' to 'function'
perf/bench: Run benchmarks, don't test them
tools/perf/bench/Build | 2 +-
tools/perf/bench/mem-functions.c | 379 +++++++++++++++++++++++++++++++++++++++++++++++++
tools/perf/bench/mem-memcpy.c | 434 ---------------------------------------------------------
tools/perf/bench/numa.c | 4 +-
tools/perf/bench/sched-messaging.c | 10 +-
tools/perf/builtin-bench.c | 14 +-
6 files changed, 394 insertions(+), 449 deletions(-)
create mode 100644 tools/perf/bench/mem-functions.c
delete mode 100644 tools/perf/bench/mem-memcpy.c
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists