19 Jan
2006
19 Jan
'06
1:26 a.m.
On Wed, 2006-01-18 at 21:22 -0800, Mike Taht wrote:
The maximum scheduling latency was 31.177 msec.
Finding out
what caused it strikes me as an intensive exercise... and I don't
think anyone in their right mind would run a workload like this.
It's actually not hard at all, and would be interesting to know.
Just enable the latency tracing options in the kernel configuration,
reset the tracer on boot with "echo 0
/proc/sys/kernel/preempt_max_latency", and post
the contents
of /proc/latency trace after generating some xruns.
Lee