From: William Lee Irwin III <wli@holomorphy.com>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: Erich Focht <efocht@hpce.nec.com>,
LSE <lse-tech@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Lse-tech] [patch 2.6.0-test1] per cpu times
Date: Fri, 18 Jul 2003 12:57:47 -0700 [thread overview]
Message-ID: <20030718195747.GU8121@holomorphy.com> (raw)
In-Reply-To: <20030718111850.C1627@w-mikek2.beaverton.ibm.com>
On Fri, Jul 18, 2003 at 11:18:50AM -0700, Mike Kravetz wrote:
> On a somewhat related note ...
> We (Big Blue) have a performance reporting application that
> would like to know how long a task sits on a runqueue before
> it is actually given the CPU. In other words, it wants to
> know how long the 'runnable task' was delayed due to contention
> for the CPU(s). Of course, one could get an overall feel for
> this based on total runqueue length. However, this app would
> really like this info on a per-task basis.
> Does anyone else think this type of info would be useful?
> A patch to compute/export this info should be straight forward
> to implement.
I wrote something to collect the standard queueing statistics a while
back but am not sure what I did with it. I think Rick Lindsley might
still have a copy around.
-- wli
next prev parent reply other threads:[~2003-07-18 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 16:35 [patch 2.6.0-test1] per cpu times Erich Focht
2003-07-18 18:18 ` [Lse-tech] " Mike Kravetz
2003-07-18 19:57 ` William Lee Irwin III [this message]
2003-07-18 20:53 ` Rick Lindsley
2003-07-21 4:47 ` Peter Chubb
2003-07-23 21:50 ` bill davidsen
2003-07-23 23:32 ` Peter Chubb
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=20030718195747.GU8121@holomorphy.com \
--to=wli@holomorphy.com \
--cc=efocht@hpce.nec.com \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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