linux-kernel - Re: [RFC][PATCH 7/7] Adding general performance benchmarking subsystem to perf.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091103172407.GA11535@elte.hu>
Date:	Tue, 3 Nov 2009 18:24:07 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Hitoshi Mitake <mitake@....info.waseda.ac.jp>
Cc:	linux-kernel@...r.kernel.org, rusty@...tcorp.com.au,
	tglx@...utronix.de, a.p.zijlstra@...llo.nl, efault@....de,
	acme@...hat.com, fweisbec@...il.com
Subject: Re: [RFC][PATCH 7/7] Adding general performance benchmarking
	subsystem to perf.


* Hitoshi Mitake <mitake@....info.waseda.ac.jp> wrote:

> > There will be a handful of more details i'm sure but once there's a 
> > good base we can commit it - would you / will you be interested in 
> > extending it further and adding more benchmark modules as well?
> > 
> > There's quite a few useful small benchmarks that people are using to 
> > measure the kernel. Having a good collection of them in one place, 
> > with standardized options and standardized output would be very 
> > useful.
> 
> Yes, of course! Unified benchmarking utilities will be big help for 
> Linux users including me.
> 
> e.g. I think that copybench (http://code.google.com/p/copybench/) will 
> be good benchmark for I/O, memory and file system. I'll work on this 
> after that the patch series I'll send later is merged.

copybench is listed as 'new BSD license'. Might need the pinging of its 
author whether he considers it GPLv2 compatible.

> Do you know any other good candidates to include?

Frederic suggested dbench - although that's quite large as it includes a 
complete trace of a benchmark run.

We might want to do similar measurements to lmbench.

One nice thing would be to have a 'system call benchmark' set - one that 
measures _all_ system calls, and could thus be used to find regressions 
on a 'broad' basis. Syscall usage could be gleaned from the LTP project.

	Ingo
--
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/