Messages in this thread | | | Subject | Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4] | Date | Fri, 29 Oct 2004 07:26:56 -0400 | From | Paul Davis <> |
| |
>my main suspicion is that either the main jackd thread itself calls the >kernel where the kernel (unexpectedly for jackd) schedules away for >whatever reason, or that the chain of wakeup in the audio path somehow >gets violated (i.e. a kernel problem). There's one quick thing we could
the "max delay" measurement isn't a reflection of the runtime activity of jackd. its simply a measurement of the delay between when jackd expected to be next woken from poll and when it actually was.
as you noted, jackd generally goes back to sleep in poll typically a long time before the next interrupt is expected. hence any delay in the wakeup is between the interrupt handler and the scheduler getting jackd's main thread back on the processor. i think.
- 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/
| |