Messages in this thread |  | | Subject | Re: [patch] voluntary-preempt-2.6.8-rc3-O5 | | From | Lee Revell <> | | Date | Thu, 12 Aug 2004 20:55:30 -0400 |
| |
On Thu, 2004-08-12 at 20:55, Florian Schmidt wrote: > i think that the mlockall and client/jackd startup xruns often do not > seem to correspond to a critical timing report.. Try the following: turn > off xrun_debug but leave the preempt-timing stuff on. On my system, the > mlockall_test provokes an xrun in jackd's output but i do not get a > preempt-timing report (thresh = 500). > > OTOH when the xrun_debug is on, the xrun_debug report actually seems to > trigger the preempt-timing report. >
Even if it is not a long non-preemptible section, mlockall-test is still doing *something* that causes an xrun in jackd. Maybe interrupts are being disabled for a long time. Whatever it is, it cannot possibly be a jackd bug, because mlockall by an unrelated, normal-priority process causes an xrun in the SCHED_FIFO jackd process.
Lee
- 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/
|  |