mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: linux-kernel@vger.kernel.org, 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
Subject: Re: [PATCH 2/3] perf-bench: add futex-wake microbenchmark
Date: Mon, 16 Dec 2013 14:25:30 +0900	[thread overview]
Message-ID: <87k3f5gyet.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1387081917-9102-3-git-send-email-davidlohr@hp.com> (Davidlohr Bueso's message of "Sat, 14 Dec 2013 20:31:56 -0800")

Hi Davidlohr,

On Sat, 14 Dec 2013 20:31:56 -0800, Davidlohr Bueso wrote:
> Block a bunch of threads on a futex and wake them up, N at a time.
>
> This program is particularly useful to measure the latency of nthread wakeups
> in non-error situations:  all waiters are queued and all wake calls wakeup
> one or more tasks. An example run:
>
> $ perf bench futex -t 512 -r 100

Did you mean 'perf bench futex wake'?

Thanks,
Namhyung

  reply	other threads:[~2013-12-16  5:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-15  4:31 [PATCH 0/3] perf-bench: introduce futex microbenchmarks Davidlohr Bueso
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 [this message]
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=87k3f5gyet.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=Waiman.Long@hp.com \
    --cc=acme@ghostprotocols.net \
    --cc=aswin@hp.com \
    --cc=davidlohr@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
Powered by JetHome