From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Paul Mackerras <paulus@samba.org>,
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: Sat, 21 Mar 2009 16:52:02 +0100 [thread overview]
Message-ID: <20090321155202.GA6356@elte.hu> (raw)
In-Reply-To: <20090321055252.eb0673ea.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> > + u64 time_enabled;
> > + u64 time_running;
>
> These look like times. I see no indication (here) as to the units.
>
> > + u64 start_enabled;
>
> This looks like a boolean, but it's u64.
>
> > + u64 start_running;
>
> hard to say.
>
> > + u64 last_stopped;
>
> probably a time, unknown units.
>
>
> 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.
What we use in the scheduler is "sum_time" or "runtime". A bit of a
tongue twister but unambiguous.
Ingo
next prev parent reply other threads:[~2009-03-21 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 12:04 [PATCH v2] perfcounters: record time running and time enabled for each counter Paul Mackerras
2009-03-21 12:52 ` Andrew Morton
2009-03-21 15:52 ` Ingo Molnar [this message]
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
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=20090321155202.GA6356@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.