lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Nov 2009 14:17:38 +0100
From:	Ingo Molnar <>
To:	Hitoshi Mitake <>
	Peter Zijlstra <>,
	Paul Mackerras <>,
	Frédéric Weisbecker 
Subject: Re: [PATCH 0/3] perf bench: Clean and add document for perf-bench

* Hitoshi Mitake <> wrote:

> This patch series cleans bench/bench.h for readability and
> adds new document describing perf-bench.
> Hitoshi Mitake (3):
>   perf bench: Clean bench/bench.h
>   perf bench: Add new document of perf-bench
>   perf bench: Modify command-list.txt for the entry of perf-bench
>  tools/perf/Documentation/perf-bench.txt |  120 +++++++++++++++++++++++++++++++
>  tools/perf/bench/bench.h                |   16 ++---
>  tools/perf/command-list.txt             |    1 +
>  3 files changed, 128 insertions(+), 9 deletions(-)
>  create mode 100644 tools/perf/Documentation/perf-bench.txt

Applied, thanks!

Btw., a small detail i noticed when running the pipe benchmark:

earth4:~/tip/tools/perf> ./perf bench sched pipe
(executing 1000000 pipe operations between two tasks)

	Total time:5.076 sec
		5.076232 usecs/op
		196996 ops/sec

when i typed 'perf bench sched pipe' nothing happened for several 
seconds. The command did not finish and no output was printed.

This might surprise users - it's always good to print a single line that 
we are processing a benchmark. Maybe this could be printed from the 
generic subcommand, something like:

  running sched/pipe benchmark ...

What do you think?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists