Thanks Lee. That's very compatible with my back-of-the-envelope
Lee Revell wrote:
I understand that there is probably a few microseconds extra delay as
the system determines that there are two interrupt devices pending. How
long is it, however, before the UCB interrupt handler does all it's work
and hands off to the sound card interrupt handler (or sound card driver)
so that it can get started?
I grant you that this will should not amount to 500uS worth of delay,
but then we need to add in the possibilities of other, higher priority
interrupts coming along during that window and further delaying the
sound card getting it's work don before the Jack frame runs out.
For me this is not a mere curiosity. Yesterday I brought up FC2 and
then, with much help from Steve Harris and Fernando, got a new Planet
kernel installed. No sooner than I had started Jack I then started using
my USB mouse and getting huge xruns. Since USB is shared with the sound
chip I think it's an example of what we ae talking about here.
to be clear I do not think the results are completely valid as the
machine has not yet been optimized, it's running KDE, arts is trying to
start at odd times, etc., but clearly there was a relationship between
my mouse and my xruns.
(Some xruns were on the order of 100-500mS!! This cannot be truly