* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > Until now users had little direct recourse to get such problems
> > fixed. (we had sysrq-t, but that included no real metric of how long
> > a task was
>
> Actually task delay accounting can measure this now. iirc someone had
> a latencytop based on it already.
Delay accounting (or the /proc/<PID>/sched fields that i added recently)
only get updated once a task has finished its unreasonably long delay
and has scheduled. So lockups or extremely long delays _wont be
detected_ this way. This is a debugging facility that clearly belongs
into the kernel. Your arguments just make no objective sense.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
