All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <davidlohr@hp.com>
To: acme@kernel.org, jolsa@kernel.org
Cc: mitake@dcl.info.waseda.ac.jp, davidlohr@hp.com, aswin@hp.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/9] perf bench: Updates for 3.17
Date: Mon, 16 Jun 2014 11:14:18 -0700	[thread overview]
Message-ID: <1402942467-10671-1-git-send-email-davidlohr@hp.com> (raw)

First set of various updates for the perf-bench tool. I am
in the process of adding more benchmarks (ipc & futex) but
wanted to get these changes in early in the -rc cycle.

Patches 3 & 5 depend on the first patch, otherwise updates
are pretty much without order.

Please consider applying.

Thanks!

Davidlohr Bueso (9):
  perf bench: Add --repeat option
  perf bench: sched-messaging: Redo runtime output
  perf bench: sched-messaging: Support multiple runs
  perf bench: sched-messaging: Plug memleak
  perf bench: futex: Use global --repeat option
  perf bench: futex: Replace --silent option with global --format
  perf bench: mem: -o and -n options are mutually exclusive
  perf bench: sched-messaging: Drop barf()
  perf bench: futex: Support operations for shared futexes

 tools/perf/Documentation/perf-bench.txt |   4 +
 tools/perf/bench/bench.h                |   1 +
 tools/perf/bench/futex-hash.c           |  39 ++++++---
 tools/perf/bench/futex-requeue.c        |  58 ++++++++-----
 tools/perf/bench/futex-wake.c           |  52 ++++++-----
 tools/perf/bench/mem-memcpy.c           |   5 ++
 tools/perf/bench/mem-memset.c           |   5 ++
 tools/perf/bench/sched-messaging.c      | 149 ++++++++++++++++++--------------
 tools/perf/builtin-bench.c              |   7 ++
 9 files changed, 196 insertions(+), 124 deletions(-)

-- 
1.8.1.4


             reply	other threads:[~2014-06-16 18:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 18:14 Davidlohr Bueso [this message]
2014-06-16 18:14 ` [PATCH 1/9] perf bench: Add --repeat option Davidlohr Bueso
2014-06-19  6:14   ` Namhyung Kim
2014-06-19 11:45     ` Davidlohr Bueso
2014-06-19 23:51       ` Namhyung Kim
2014-06-20  3:03         ` Davidlohr Bueso
2014-06-24  5:54           ` Namhyung Kim
2014-06-25  5:51   ` [tip:perf/core] " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 2/9] perf bench: sched-messaging: Redo runtime output Davidlohr Bueso
2014-06-19 19:30   ` Arnaldo Carvalho de Melo
2014-06-16 18:14 ` [PATCH 3/9] perf bench: sched-messaging: Support multiple runs Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 4/9] perf bench: sched-messaging: Plug memleak Davidlohr Bueso
2014-06-19  6:20   ` Namhyung Kim
2014-06-25  5:51   ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 5/9] perf bench: futex: Use global --repeat option Davidlohr Bueso
2014-06-25  5:51   ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 6/9] perf bench: futex: Replace --silent option with global --format Davidlohr Bueso
2014-06-19 16:38   ` Arnaldo Carvalho de Melo
2014-06-19 17:01     ` Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 7/9] perf bench: mem: -o and -n options are mutually exclusive Davidlohr Bueso
2014-06-25  5:52   ` [tip:perf/core] perf bench mem: The " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 8/9] perf bench: sched-messaging: Drop barf() Davidlohr Bueso
2014-06-25  5:52   ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 9/9] perf bench: futex: Support operations for shared futexes Davidlohr Bueso
2014-06-19 16:41   ` Arnaldo Carvalho de Melo
2014-06-19 16:43     ` Davidlohr Bueso
2014-06-19 17:05       ` Arnaldo Carvalho de Melo
2014-06-19 19:48         ` Darren Hart
2014-06-25 17:07         ` Davidlohr Bueso

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=1402942467-10671-1-git-send-email-davidlohr@hp.com \
    --to=davidlohr@hp.com \
    --cc=acme@kernel.org \
    --cc=aswin@hp.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitake@dcl.info.waseda.ac.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.