From: Davidlohr Bueso <dave@stgolabs.net>
To: acme@kernel.org
Cc: james.yang@arm.com, kim.phillips@arm.com, dave@stgolabs.net,
linux-kernel@vger.kernel.org
Subject: [PATCH -tip 0/3] perf bench futex: Improvements
Date: Sun, 26 Nov 2017 20:20:58 -0800 [thread overview]
Message-ID: <20171127042101.3659-1-dave@stgolabs.net> (raw)
Hi,
I'm resending the patches from James Yang and Kim Phillips that
improve the perf bench futex benchmarks. Noticibly:
patch1 makes use of util/cpumap.c
patch2/3 are the same as the original only that I've split
it into two and removed some bogus debug noise.
Davidlohr Bueso (3):
perf bench futex: Use cpumaps
perf bench futex: Add --affine-wakers option to wake-parallel
perf bench futex: sync waker threads
tools/perf/bench/futex-hash.c | 19 ++++++++-----
tools/perf/bench/futex-lock-pi.c | 23 +++++++++------
tools/perf/bench/futex-requeue.c | 22 +++++++++------
tools/perf/bench/futex-wake-parallel.c | 51 ++++++++++++++++++++++++++--------
tools/perf/bench/futex-wake.c | 18 +++++++-----
5 files changed, 90 insertions(+), 43 deletions(-)
--
2.13.6
next reply other threads:[~2017-11-27 4:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 4:20 Davidlohr Bueso [this message]
2017-11-27 4:20 ` [PATCH 1/3] perf bench futex: Use cpumaps Davidlohr Bueso
2017-12-06 16:34 ` [tip:perf/core] " tip-bot for Davidlohr Bueso
2017-11-27 4:21 ` [PATCH 2/3] perf bench futex: Add --affine-wakers option to wake-parallel Davidlohr Bueso
2017-12-06 17:24 ` Davidlohr Bueso
2017-11-27 4:21 ` [PATCH 3/3] perf bench futex: sync waker threads Davidlohr Bueso
2017-12-06 16:35 ` [tip:perf/core] perf bench futex: Sync " tip-bot for James Yang
2017-11-28 3:20 ` [PATCH -tip 0/3] perf bench futex: Improvements Kim Phillips
2017-11-30 17:00 ` 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=20171127042101.3659-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=acme@kernel.org \
--cc=james.yang@arm.com \
--cc=kim.phillips@arm.com \
--cc=linux-kernel@vger.kernel.org \
/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®