lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 03 Nov 2009 13:26:14 +0900 (JST)
From:	Hitoshi Mitake <mitake@....info.waseda.ac.jp>
To:	efault@....de
Cc:	mingo@...e.hu, rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, a.p.zijlstra@...llo.nl, acme@...hat.com,
	fweisbec@...il.com
Subject: Re: [PATCH][RFC] Adding benchmark subsystem to perf

From: Mike Galbraith <efault@....de>
Subject: Re: [PATCH][RFC] Adding benchmark subsystem to perf
Date: Mon, 02 Nov 2009 15:26:09 +0100

> Hi,
> 
> On Mon, 2009-11-02 at 22:51 +0900, Hitoshi Mitake wrote:
> 
> > Example of usage:
> > % perf bench sched -t -l 1000
> > 2.863
> 
> I think this should allow other benchmarks to be added is a logical
> manner.  Perhaps perf bench -t hackbench -t -l 1000, ie bench should
> process args to allow the user to select a benchmark from a suite, and
> pass args to it as well, but with a default set built in so people can
> just type perf bench -t foo, to run any benchmark with it's defaults.

Thanks for your comment, Mike.

I forgot to do that. So I prepared new patch series
to implement your suggestion.

The new patch series containts new benchmark program,
based on Ingo's pipe-test-1m.c
http://people.redhat.com/mingo/cfs-scheduler/tools/pipe-test-1m.c

And the series became too big to pack into one mail.
So I'll send it in new thread. Please wait a minute.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ