All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
To: Florian Schmidt <mista.tapas-hi6Y0CQ0nG0@public.gmane.org>
Cc: ico-rDkNP/OoUoU@public.gmane.org,
	alsa-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	The Linux Audio Developers' Mailing List
	<linux-audio-dev-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org>,
	Paul Davis
	<paul-dDzkXPnfpdxaomM2pvQuqZqQE7yCjDx5@public.gmane.org>
Subject: Re: [Alsa-devel] Re: snd-hdsp oddities
Date: Fri, 02 Jul 2004 14:30:04 +0200	[thread overview]
Message-ID: <s5h1xjua8xf.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040702132644.3697ed1d-1azMibUuNldkksQ3EBHwWw@public.gmane.org>

At Fri, 2 Jul 2004 13:26:44 +0200,
Florian Schmidt wrote:
> 
> On Fri, 02 Jul 2004 11:40:28 +0200
> Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org> 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

  parent reply	other threads:[~2004-07-02 12:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02  0:22 snd-hdsp oddities ico-rDkNP/OoUoU
     [not found] ` <20040702002208.KXUI17933.smtp2.fuse.net-TAIDijpykVYqcZcGjlUOXw@public.gmane.org>
2004-07-02  2:16   ` Paul Davis
2004-07-02  7:32     ` Re: [linux-audio-dev] " Russell King
     [not found]     ` <200407020216.i622GdaC002355-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-07-02  9:40       ` [Alsa-devel] " Takashi Iwai
     [not found]         ` <s5h7jtmags3.wl-UC7Roit8zEholqkO4TVVkw@public.gmane.org>
2004-07-02 11:26           ` Florian Schmidt
     [not found]             ` <20040702132644.3697ed1d-1azMibUuNldkksQ3EBHwWw@public.gmane.org>
2004-07-02 12:30               ` Takashi Iwai [this message]
2004-07-05 12:00 ` Russell King
2004-07-05 15:51   ` Ivica Ico Bukvic
  -- strict thread matches above, loose matches on Subject: below --
2004-07-02 12:56 ico-rDkNP/OoUoU
2004-07-02 13:15 ` Re: [linux-audio-dev] " Takashi Iwai
     [not found]   ` <s5hwu1m8s8t.wl-UC7Roit8zEholqkO4TVVkw@public.gmane.org>
2004-07-02 13:55     ` [Alsa-devel] " Florian Schmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h1xjua8xf.wl@alsa2.suse.de \
    --to=tiwai-l3a5bk7wagm@public.gmane.org \
    --cc=alsa-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ico-rDkNP/OoUoU@public.gmane.org \
    --cc=linux-audio-dev-oG0YroN0ZiqENrSoib9kfje48wsgrGvP@public.gmane.org \
    --cc=mista.tapas-hi6Y0CQ0nG0@public.gmane.org \
    --cc=paul-dDzkXPnfpdxaomM2pvQuqZqQE7yCjDx5@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.