All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Chubb <peter@chubb.wattle.id.au>
To: davidsen@tmr.com (bill davidsen)
Cc: linux-kernel@vger.kernel.org, kravetz@us.ibm.com
Subject: Re: [Lse-tech] [patch 2.6.0-test1] per cpu times
Date: Thu, 24 Jul 2003 09:32:48 +1000	[thread overview]
Message-ID: <16159.6944.889606.686405@wombat.chubb.wattle.id.au> (raw)
In-Reply-To: <bfmvvi$lba$1@gatekeeper.tmr.com>

>>>>> "bill" == bill davidsen <davidsen@tmr.com> writes:
>>>>> "Mike" == Mike Kravetz  <kravetz@us.ibm.com>

Mike> On a somewhat related note ...  We (Big Blue) have a
Mike> performance reporting application that would like to know how
Mike> long a task sits on a runqueue before it is actually given the
Mike> CPU.  In other words, it wants to know how long the 'runnable
Mike> task' was delayed due to contention for the CPU(s).  Of
Mike> course, one could get an overall feel for this based on total
Mike> runqueue length.  However, this app would really like this
Mike> info on a per-task basis.

bill> This is certainly a useful number. 

This is exactly what's measured by the microstate accounting patches
I've been pushing to LKML, along with a few other useful statistics.

If you try it, please let me know: see
http://marc.theaimsgroup.com/?l=linux-kernel&m=105884469205748&w=2


--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories,   all slightly different.

      reply	other threads:[~2003-07-23 23:17 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
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 [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=16159.6944.889606.686405@wombat.chubb.wattle.id.au \
    --to=peter@chubb.wattle.id.au \
    --cc=davidsen@tmr.com \
    --cc=kravetz@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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.