Re: Microstate Accounting for 2.6.11
From: Peter Chubb
Date: Fri Mar 11 2005 - 00:07:16 EST
>>>>> "Andrew" == Andrew Morton <akpm@xxxxxxxx> writes:
Andrew> Peter Chubb <peterc@xxxxxxxxxxxxxxxxxx> wrote:
>> Timing data on threads at present is pretty crude: when the timer
>> interrupt occurs, a tick is added to either system time or user
>> time for the currently running thread. Thus in an unpacthed kernel
>> one can distinguish three timed states: On-cpu in userspace, on-cpu
>> in system space, and not running.
>> The actual number of states is much larger. A thread can be on a
>> runqueue or the expired queue (i.e., ready to run but not running),
>> sleeping on a semaphore or on a futex, having its time stolen to
>> service an interrupt, etc., etc.
>> This patch adds timers per-state to each struct task_struct, so
>> that time in all these states can be tracked. This patch contains
>> the core code do the timing, and to initialise the timers.
>> Subsequent patches enable the code (by adding Kconfig options) and
>> add hooks to track state changes.
Andrew> Why does the kernel need this feature?
I find that it's useful when trying to work out why a thread is going
more slowly than it needs to. Userspace tools in the CVS repository
at gelato.unsw.edu.au let you graph in real time the time spent in
each state, so you get graphs like this:
which shows mplay skipping because of a slow disk/filesystem.
Andrew> Have you any numbers on the overhead?
Around 5% on LMbench context switch numbers for uniprocessor,
negligeable on SMP (but SMP context switch results are horrible at the
moment according to LMbench2 -- almost 16usec); select on 10 fd goes
from 1.665 usec to 1.701;
Andrew> The preempt_disable() in sys_msa() seems odd.
Yes I only added that yesterday. It's to prevent migration while
updating the current timer. All the other places where the current
timer are updated are naturally protected this. It should probably be a
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/