From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Kim Phillips <kim.phillips@arm.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
james.yang@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip 0/3] perf bench futex: Improvements
Date: Thu, 30 Nov 2017 14:00:42 -0300 [thread overview]
Message-ID: <20171130170042.GP3298@kernel.org> (raw)
In-Reply-To: <20171127212005.bc4b9e7cd9a576a1c9e50691@arm.com>
Em Mon, Nov 27, 2017 at 09:20:05PM -0600, Kim Phillips escreveu:
> On Sun, 26 Nov 2017 20:20:58 -0800
> Davidlohr Bueso <dave@stgolabs.net> wrote:
>
> > I'm resending the patches from James Yang and Kim Phillips that
> > improve the perf bench futex benchmarks. Noticibly:
>
> Thanks!
> > 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
>
> They all look good to me.
Taking this as an Acked-by.
- Arnaldo
>
> I'm resubmitting 3/3 - the jvmti one - separately now.
>
> Thanks,
>
> Kim
prev parent reply other threads:[~2017-11-30 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 4:20 Davidlohr Bueso
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 [this message]
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=20171130170042.GP3298@kernel.org \
--to=acme@kernel.org \
--cc=dave@stgolabs.net \
--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
Powered by JetHome