MIME-Version: 1.0
In-Reply-To: <18885.29855.433194.463455@cargo.ozlabs.ibm.com>
References: <18884.55232.197620.696687@cargo.ozlabs.ibm.com> 
	<20090321055252.eb0673ea.akpm@linux-foundation.org> <18885.29855.433194.463455@cargo.ozlabs.ibm.com>
Date: Sun, 22 Mar 2009 10:16:53 -0700
Message-ID: <2c0942db0903221016y45c21dbeu699f666b8e3431ee@mail.gmail.com>
Subject: Re: [PATCH v2] perfcounters: record time running and time enabled for 
	each counter
From: Ray Lee <ray-lk@madrabbit.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>,
       Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 838
Lines: 18

On Sat, Mar 21, 2009 at 4:13 PM, Paul Mackerras <paulus@samba.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/