Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263257AbUJ2L1C (ORCPT ); Fri, 29 Oct 2004 07:27:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263260AbUJ2L1C (ORCPT ); Fri, 29 Oct 2004 07:27:02 -0400 Received: from out012pub.verizon.net ([206.46.170.137]:54667 "EHLO out012.verizon.net") by vger.kernel.org with ESMTP id S263257AbUJ2L07 (ORCPT ); Fri, 29 Oct 2004 07:26:59 -0400 Message-Id: <200410291126.i9TBQuFu002731@localhost.localdomain> To: Ingo Molnar cc: Thomas Gleixner , LKML , Lee Revell , mark_h_johnson@raytheon.com, Bill Huey , Adam Heath , Florian Schmidt , Michal Schmidt , Fernando Pablo Lopez-Lezcano , Karsten Wiese , jackit-devel , Rui Nuno Capela Subject: Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4] In-reply-to: Your message of "Fri, 29 Oct 2004 13:14:08 +0200." <20041029111408.GA28259@elte.hu> Date: Fri, 29 Oct 2004 07:26:56 -0400 From: Paul Davis X-Authentication-Info: Submitted using SMTP AUTH at out012.verizon.net from [141.151.88.122] at Fri, 29 Oct 2004 06:26:58 -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 993 Lines: 19 >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/