From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [Alsa-devel] Re: snd-hdsp oddities Date: Fri, 02 Jul 2004 14:30:04 +0200 Sender: linux-audio-dev-bounces-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org Message-ID: References: <20040702002208.KXUI17933.smtp2.fuse.net@smtp.fuse.net> <200407020216.i622GdaC002355@localhost.localdomain> <20040702132644.3697ed1d@mango.fruits.de> Reply-To: "The Linux Audio Developers' Mailing List" Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20040702132644.3697ed1d-1azMibUuNldkksQ3EBHwWw@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-audio-dev-bounces-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org To: Florian Schmidt Cc: ico-rDkNP/OoUoU@public.gmane.org, alsa-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, The Linux Audio Developers' Mailing List , Paul Davis List-Id: alsa-devel@alsa-project.org At Fri, 2 Jul 2004 13:26:44 +0200, Florian Schmidt wrote: > > On Fri, 02 Jul 2004 11:40:28 +0200 > Takashi Iwai wrote: > > > > When the dust settles from the kernel and NPTL, 2.6 will be more > > > viable. Right now, even though it works for some people, its not a > > > generally viable platform for realtime audio. > > > > Hmm, except for some sched policy setting problems on NPTL, I don't > > see bigger problem than 2.4+preempt kernel. For some people, > > 2.4+preempt might work _casually_ better than 2.6, but it can happen > > vice versa. > > > > Shouting "DON'T USE 2.6" isn't a good solution. Though, we need to > > inform to "set LD_ASSUME_KERNEL as a workaround"... > > Yes, but i wonder: many other people use NPTL for many kinds of > applications w/o problems.. The jack source code is too complex for me > to really find my way through it, but maybe someone might consider > summing up how jack handles threads and provide pointers into the > source at the relevant spots.. Maybe NPTL isn't at fault, but jack.. Well, it's hard to determine at this point. It could be a bug of pthread_setschedparm() on NPTL. > Also, i think it would be very useful to have simplified test case > which shows the "erraneous" behaviour of jack/NPTL.. Yes, definitely. Takashi