From: Chris Friesen <chris.friesen@genband.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: /proc/<pid>/sched should contain cumulative data for all threads in process
Date: Wed, 09 Feb 2011 11:28:33 -0600 [thread overview]
Message-ID: <4D52CEC1.2050605@genband.com> (raw)
In-Reply-To: <1297172742.13327.102.camel@laptop>
On 02/08/2011 07:45 AM, Peter Zijlstra wrote:
> On Tue, 2011-02-08 at 13:11 +0100, Ingo Molnar wrote:
>> So assuming a tool would want to capture such stats of the system, what would be its
>> options? Could we do all this via system-wide counters and perf stat alike cheap,
>> transparent gathering without having to patch/rebuild the kernel?
>
> Very much depends on what is wanted, but most of the stuff inside those
> files is very specific to the implementation and pinning any of that to
> an ABI is like silly.
Currently we're using the following fields from
/proc/<pid>/task/<tid>/sched:
sum_exec_runtime
wait_sum
wait_max
exec_max
iowait_sum
iowait_count
nr_switches
If there's a better way to get this information (with the precision
available from this interface) then I'd love to hear about it.
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
prev parent reply other threads:[~2011-02-09 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 22:29 RFC: /proc/<pid>/sched should contain cumulative data for all threads in process Chris Friesen
2011-02-08 9:21 ` Peter Zijlstra
2011-02-08 12:11 ` Ingo Molnar
2011-02-08 13:45 ` Peter Zijlstra
2011-02-08 15:14 ` Ingo Molnar
2011-02-09 17:28 ` Chris Friesen [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=4D52CEC1.2050605@genband.com \
--to=chris.friesen@genband.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.