linux-kernel - Re: [PATCH v2 3/7] Adding general performance benchmarking subcommand 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]

Date:	Mon, 09 Nov 2009 12:27:12 +0900 (JST)
From:	Hitoshi Mitake <mitake@....info.waseda.ac.jp>
To:	mingo@...e.hu
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: [PATCH v2 3/7] Adding general performance benchmarking
 subcommand to perf.

From: Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH v2 3/7] Adding general performance benchmarking subcommand to perf.
Date: Sun, 8 Nov 2009 12:30:13 +0100

> > > 
> > > Shouldnt we output the unit of measurement, i.e. '4.575 usecs'? Also, we 
> > > should perhaps print something like:
> > > 
> > >   % perf bench sched pipe
> > > 
> > >   (executing 1000000 pipe operations between two tasks)
> > > 
> > >      4.575 usecs per op
> > >     218579 ops/sec   
> > > 
> > > ?
> > 
> > I have to admit that single float value output is too simple.
> > So I'll fix the default output.
> > 
> > But, I believe that simple form makes sense for
> > processing by scripts or graph tools like gnuplot.
> > I'll add the option (may be --simple) to switch
> > friendliness of outputs.
> 
> Btw., could you make it Git-ish, i.e.:
> 
>  --format=short
> 
> or:
> 
>  --format=simple
> 
> Eventually more format options might be added.

It's good idea.
I have to admit that reserving -s for simple output is not good idea.
I'll do this.
--
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/