From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Mike Chan <mike@android.com>,
cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] sched: cpuacct: Track cpuusage per cpu frequency
Date: Tue, 6 Apr 2010 07:45:59 +0530 [thread overview]
Message-ID: <20100406021559.GD3630@balbir.in.ibm.com> (raw)
In-Reply-To: <w2l6599ad831004051252mbf8c4cedz293540bfc7b2f87a@mail.gmail.com>
* menage@google.com <menage@google.com> [2010-04-05 12:52:57]:
> On Mon, Apr 5, 2010 at 12:33 PM, Mike Chan <mike@android.com> wrote:
> > New file: cpuacct.cpufreq when CONFIG_CPU_FREQ_STATS is enabled.
> >
> > cpuacct.cpufreq accounts for cpu time per-cpu frequency, time is exported
> > in nano-seconds
>
> Can you clarify the wording of this (and describe it in the relevant
> Documentation/... file)? It's not clear.
>
> From the code, it appears that the file reports a breakdown of how
> much CPU time the cgroup has been consuming at each different CPU
> frequency level. If so, then you probably want to reword the
> description to avoid "per-cpu", since that makes it sounds as though
> it's reporting something, well, "per CPU".
>
> Also, what's the motivation here? If it's for power monitoring
> purposes, might it be simpler to just report a single number, that's
> the integral of the CPU usage by frequency index (i.e. calculated from
> the same information that this patch is already gathering in
> cpuacct_charge()) rather than dumping a whole table on userspace?
As utilization increases, won't the integral quickly overflow? BTW,
Mike have you looked at the scaled accounting infrastructure we have
in taskstats?
--
Three Cheers,
Balbir
next prev parent reply other threads:[~2010-04-06 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 19:33 [RFC][PATCH] sched: cpuacct: Track cpuusage per cpu frequency Mike Chan
2010-04-05 19:52 ` Paul Menage
2010-04-05 21:02 ` Mike Chan
2010-04-06 2:15 ` Balbir Singh [this message]
2010-04-06 2:40 ` Mike Chan
2010-04-06 2:13 ` Balbir Singh
2010-04-06 4:14 ` Mike Chan
2010-04-06 17:48 ` Daniel Walker
2010-04-06 19:43 ` Mike Chan
2010-04-06 19:58 ` Daniel Walker
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=20100406021559.GD3630@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mike@android.com \
/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