linux-kernel - Re: [PATCH v2] perfcounters: record time running and time enabled for each counter

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:	Sun, 22 Mar 2009 10:16:53 -0700
From:	Ray Lee <ray-lk@...rabbit.org>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] perfcounters: record time running and time enabled for 
	each counter

On Sat, Mar 21, 2009 at 4:13 PM, Paul Mackerras <paulus@...ba.org> wrote:
> Andrew Morton writes:
>
>> Perhaps one of the reasons why this code is confusing is the blurring
>> between the "time" at which an event occured and the "time" between the
>> occurrence of two events.  A weakness in English, I guess.  Using the term
>> "interval" in the latter case will help a lot.
>
> Except that we aren't measuring an "interval", we're measuring the
> combined length of a whole series of intervals.  What's a good word
> for that?

As Ingo pointed out, 'runtime' is a decent choice for that.
--
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/