linux-kernel - Re: [PATCH v3 3/3] perf, tools, script: Allow computing metrics in perf script

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: <20171120160306.GG28112@tassilo.jf.intel.com>
Date:   Mon, 20 Nov 2017 08:03:06 -0800
From:   Andi Kleen <ak@...ux.intel.com>
To:     Jiri Olsa <jolsa@...hat.com>
Cc:     Andi Kleen <andi@...stfloor.org>, acme@...nel.org,
        jolsa@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] perf, tools, script: Allow computing metrics in
 perf script

> > Yes it is.
> > 
> > It's for the complete sampling period because it is computed
> > over the delta from the last sample to the previous sample.
> > 
> > There isn't really a metric at a point, it is always over a interval.
> 
> agreed, it's the count we meassured from the last sample.. but the
> 'averaged' word above implies to me we compute some average over the
> 'sampling' period, which we dont do

Do you have a better word in mind?

AFAIK average is the right word for this because it's the summary
for that time period.

-Andi