On Fri, Jun 19, 2009 at 08:45:12AM +0200, Stéphane Letz wrote:
this discussion seems to go away from the real issue to implementation
details of pa.
however the deeper i read into stuff which is being called, the more
malloc and mutex_lock() i see.
even with jack_cycle_signal we are having a thread, which is running at
the same priority as other jack threads, so it still has a certein
potential to choke the other jack clients.
first of all.... lets assume jack is running with -p64 -n2
i am not sure if lennart is aware that jack often runs with such
latencies. i dont really care for event processing inside the RT loop.
however you cant know how many clients are following in the process
cycle, so you cant know a sane threshold value.
what i am asking for is that events are either passed into your RT loop
via lock-free fifos, or you decouple your soft-RT stuff from jacks RT
stuff, which is not as soft as you think.
at least nobody is creating semaphores in jack_process code.
if you insist on soft-RT behaviour, just decouple and do what you want.
http://galan.sourceforge.net -- The graphical Audio language
Linux-audio-dev mailing list