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
Subject: Re: [PATCH v2] perfcounters: record time running and time enabled for each counter
Date: Sun, 22 Mar 2009 10:16:53 -0700 [thread overview]
Message-ID: <2c0942db0903221016y45c21dbeu699f666b8e3431ee@mail.gmail.com> (raw)
In-Reply-To: <18885.29855.433194.463455@cargo.ozlabs.ibm.com>
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.
prev parent reply other threads:[~2009-03-22 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 12:04 Paul Mackerras
2009-03-21 12:52 ` Andrew Morton
2009-03-21 15:52 ` Ingo Molnar
2009-03-21 15:54 ` Ingo Molnar
2009-03-21 16:10 ` [tree] Performance Counters for Linux, v7 Ingo Molnar
2009-03-22 6:48 ` Jaswinder Singh Rajput
2009-03-23 22:06 ` Ingo Molnar
2009-03-21 23:13 ` [PATCH v2] perfcounters: record time running and time enabled for each counter Paul Mackerras
2009-03-22 8:55 ` Andrew Morton
2009-03-22 11:44 ` Paul Mackerras
2009-03-22 17:16 ` Ray Lee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c0942db0903221016y45c21dbeu699f666b8e3431ee@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®