From: Davidlohr Bueso <davidlohr@hp.com>
To: linux-kernel@vger.kernel.org
Cc: acme@ghostprotocols.net, mingo@redhat.com,
dvhart@linux.intel.com, peterz@infradead.org, tglx@linutronix.de,
jason.low2@hp.com, Waiman.Long@hp.com, scott.norton@hp.com,
aswin@hp.com, davidlohr@hp.com
Subject: [PATCH 0/3] perf-bench: introduce futex microbenchmarks
Date: Sat, 14 Dec 2013 20:31:54 -0800 [thread overview]
Message-ID: <1387081917-9102-1-git-send-email-davidlohr@hp.com> (raw)
This patchset adds three programs that stress and measure different futex
operations: (i) uaddr hashing, (ii) wakeups and (iii) requeuing/waiting.
More details and usage examples in each individual patch, along with parameter
descriptions in the code.
While the previous effort (https://lkml.org/lkml/2012/5/17/207) to add futex
benchmarks to perf-bench failed, I strongly believe that perf is an ideal place
for these kinds of programs. This patchset is different from Hitoshi's because
it does not try to take over Darren's futextest suite, and only deals with
finer grained aspects of the kernel's implementation, and thus mostly useful
for kernel hacking. Furthermore, by being part of the kernel tree, it can get
more attention and naturally evolve with time.
Thanks!
Davidlohr Bueso (3):
perf-bench: add futex-hash microbenchmark
perf-bench: add futex-wake microbenchmark
perf-bench: add futex-requeue microbenchmark
tools/perf/Makefile.perf | 3 +
tools/perf/bench/bench.h | 3 +
tools/perf/bench/futex-hash.c | 212 +++++++++++++++++++++++++++++++++++++++
tools/perf/bench/futex-requeue.c | 211 ++++++++++++++++++++++++++++++++++++++
tools/perf/bench/futex-wake.c | 201 +++++++++++++++++++++++++++++++++++++
tools/perf/bench/futex.h | 71 +++++++++++++
tools/perf/builtin-bench.c | 12 ++-
tools/perf/perf.h | 6 ++
8 files changed, 718 insertions(+), 1 deletion(-)
create mode 100644 tools/perf/bench/futex-hash.c
create mode 100644 tools/perf/bench/futex-requeue.c
create mode 100644 tools/perf/bench/futex-wake.c
create mode 100644 tools/perf/bench/futex.h
--
1.8.1.4
next reply other threads:[~2013-12-15 4:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 4:31 Davidlohr Bueso [this message]
2013-12-15 4:31 ` [PATCH 1/3] perf-bench: add futex-hash microbenchmark Davidlohr Bueso
2014-03-18 8:28 ` [tip:perf/core] perf bench: Add " tip-bot for Davidlohr Bueso
2013-12-15 4:31 ` [PATCH 2/3] perf-bench: add futex-wake microbenchmark Davidlohr Bueso
2013-12-16 5:25 ` Namhyung Kim
2013-12-16 14:45 ` Davidlohr Bueso
2014-03-18 8:28 ` [tip:perf/core] perf bench: Add " tip-bot for Davidlohr Bueso
2013-12-15 4:31 ` [PATCH 3/3] perf-bench: add futex-requeue microbenchmark Davidlohr Bueso
2014-03-18 8:28 ` [tip:perf/core] perf bench: Add " tip-bot for Davidlohr Bueso
2013-12-16 10:08 ` [PATCH 0/3] perf-bench: introduce futex microbenchmarks Ingo Molnar
2013-12-16 14:44 ` Davidlohr Bueso
2014-01-24 18:13 ` Darren Hart
2014-01-28 4:12 ` Davidlohr Bueso
2014-01-28 12:12 ` Arnaldo Carvalho de Melo
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=1387081917-9102-1-git-send-email-davidlohr@hp.com \
--to=davidlohr@hp.com \
--cc=Waiman.Long@hp.com \
--cc=acme@ghostprotocols.net \
--cc=aswin@hp.com \
--cc=dvhart@linux.intel.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--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
all inboxes | Powered by JetHome®