On Tuesday 02 December 2003 02.50, Jack O'Quin wrote:
Roger Larsson <roger.larsson(a)norran.net>
writes:
But it is still a way to see that no client burns
cycles where it should
not - jackd would not start (or stop). And you _can_ get fewer context
switches, but only if some client burns extra cycles.
Compare:
With jackd as highest priority:
Context switches: A->jd [start B] ->A [tail] ->B->jd
With jackd as lowest priority:
Context switches: A->jd->B->jd
The actual JACK process cycle works like this:
jd->A->B->jd
How?
How can B start immediately after A without ANY
jackd running in between?
(I am talking about external clients)
/RogerL
--
Roger Larsson
SkellefteƄ
Sweden