In article <20030718111850.C1627@w-mikek2.beaverton.ibm.com>,
Mike Kravetz <kravetz@us.ibm.com> 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.
This is certainly a useful number. It's easy to tell when the CPU is "in
use," but it's not easy to tell when it's "busy" and processes are
waiting for a CPU.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:50 EST