| commit | 6d082592b62689fb91578d0338d04a9f50991990 | |
| author | Arjan van de Ven <arjan@linux.intel.com> | |
| Fri, 25 Jan 2008 20:08:35 +0000 (25 21:08 +0100) | ||
| committer | Ingo Molnar <mingo@elte.hu> | |
| Fri, 25 Jan 2008 20:08:35 +0000 (25 21:08 +0100) | ||
| tree | facef621798752724be64c3ded31a3c3fded1643 | treesnapshot (tar.gz zip) |
| parent | 286100a6cf1c1f692e5f81d14b364ff12b7662f5 | commitdiff |
sched: keep total / count stats in addition to the max for
Right now, the linux kernel (with scheduler statistics enabled) keeps track
of the maximum time a process is waiting to be scheduled. While the maximum
is a very useful metric, tracking average and total is equally useful
(at least for latencytop) to figure out the accumulated effect of scheduler
delays. The accumulated effect is important to judge the performance impact
of scheduler tuning/behavior.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Right now, the linux kernel (with scheduler statistics enabled) keeps track
of the maximum time a process is waiting to be scheduled. While the maximum
is a very useful metric, tracking average and total is equally useful
(at least for latencytop) to figure out the accumulated effect of scheduler
delays. The accumulated effect is important to judge the performance impact
of scheduler tuning/behavior.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
| include/linux/sched.h | diffblobblamehistory | |
| kernel/sched_debug.c | diffblobblamehistory | |
| kernel/sched_fair.c | diffblobblamehistory |