From: "Gregory Haskins" <ghaskins@novell.com>
To: "Ankita Garg" <ankita@in.ibm.com>, <linux-kernel@vger.kernel.org>
Cc: "Ingo Molnar" <mingo@elte.hu>, <rostedt@goodmis.org>,
"Peter Zijlstra" <peterz@infradead.org>,
<suresh.b.siddha@intel.com>, <aneesh.kumar@linux.vnet.ibm.com>,
<dhaval@linux.vnet.ibm.com>, <vatsa@linux.vnet.ibm.com>,
"David Bahi" <DBahi@novell.com>
Subject: [ANNOUNCE] sched: schedtop utility v0.3
Date: Mon, 02 Jun 2008 21:21:37 -0600 [thread overview]
Message-ID: <48448081.BA47.005A.0@novell.com> (raw)
In-Reply-To: 483545B4.BA47.005A.0@novell.com
>>> On Thu, May 22, 2008 at 10:06 AM, in message <483545B4.BA47.005A.0@novell.com>,
Gregory Haskins wrote:
> Hi all scheduler developers,
> I had an itch to scratch w.r.t. watching the stats in /proc/schedstats,
> and it appears that the perl scripts referenced in
> Documentation/scheduler/sched-stats.txt do not support v14 from HEAD so I
> whipped up a little utility I call "schedtop".
>
> This utility will process statistics from /proc/schedstat such that the
> busiest stats will bubble up to the top. It can alternately be sorted by the
> largest stat, or by name. Stats can be included or excluded based on reg-ex
> pattern matching.
>
> You can download the tarball here:
>
> ftp://ftp.novell.com/dev/ghaskins/schedtop.tar.gz
>
> I have also posted it to the opensuse build service for generating RPMS for
> a handful of 32/64-bit x86 distros for your convenience:
>
> http://download.opensuse.org/repositories/home:/ghaskins/
>
> (Note that the build is still in progress for some of the favors, so if you
> do not see the flavor you are looking for, check back in a little while)
>
> Comments/feedback/bug-fixes welcome!
>
> Regards
> -Greg
Hi All,
I have posted an update to schedtop (v0.3) which adds /proc/<pid>/schedstats and /proc/<pid>/sched stats to the mix.
Also note that there is a comprehensive filtering mechanism built into all versions of schedtop:
"-i <REGEX>" sets the *include* pattern, and
"-x <REGEX> sets the *exclude* pattern.
By default, -i is set to allow everything, and -x is set to exclude nothing. A common config for me is to use "-x sched_info" since those sched_info stats seem to always be moving rapidly and can cloud stats that are more interesting (to me, anyway).
Let me know if you have any questions. Comments/feedback are welcome
-Greg
next prev parent reply other threads:[~2008-06-03 3:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 14:06 [ANNOUNCE] sched: schedtop utility Gregory Haskins
2008-05-22 14:33 ` Steven Rostedt
2008-06-02 12:48 ` Ankita Garg
2008-06-02 13:07 ` Peter Zijlstra
2008-06-02 13:20 ` Gregory Haskins
2008-06-05 5:20 ` Ankita Garg
2008-06-19 10:27 ` Peter Zijlstra
2008-07-01 9:00 ` Ankita Garg
2008-07-03 8:34 ` Ingo Molnar
2008-07-03 20:56 ` Peter Zijlstra
2008-10-21 16:29 ` Gregory Haskins
2008-06-03 3:21 ` Gregory Haskins [this message]
2008-06-17 12:18 ` [ANNOUNCE] sched: schedtop utility v0.5 Gregory Haskins
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=48448081.BA47.005A.0@novell.com \
--to=ghaskins@novell.com \
--cc=DBahi@novell.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ankita@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=suresh.b.siddha@intel.com \
--cc=vatsa@linux.vnet.ibm.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