linux-kernel - Re: [PATCH -tip] perf_counter tools: shorten names for events

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:	Thu, 25 Jun 2009 17:34:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] perf_counter tools: shorten names for events


* Roland Dreier <rdreier@...co.com> wrote:

>  >       266590464  L1d-loads             (scaled from 23.03%)
> 
> IMHO "L1d" is too abbreviated for it to be obvious that it means 
> L1 data cache.  If you want something really short maybe "L1-d$" 
> might be a little clearer, but I stil like "L1-dcache" best.

i changed it to L1-d$ / L1-i$.

> The formatting of aligning things is nice defitely but we could 
> also shorten lines by saying "scaled from" in fewer characters 
> maybe?  (I have to admit I don't know what "scaled from X%" means 
> in this case so I can't suggest something better, but the fact 
> that I can't easily tell what it means probably suggests that the 
> wording could be improved)

Indeed, the '(scaled from 12.3%)' message should i guess be changed 
to:

  (9.43x scaled)

( and a multiplicative factor is more expressive anyway, than the 
  percentage of from where we scale up. )

	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/