On Monday 11 July 2011 23:15:26 Tim E. Real wrote:
> On July 11, 2011 04:50:06 pm Chris Cannam wrote:
> > I know taking locks in a RT process is deeply frowned upon
> 
> Likely been answered before, but good time for me to ask:
> What is the reason it is not recommended?
> Is it simply because of a long time involved in acquiring the lock, or is
> it because the lock might block some other Jack thread from running?
> The same reason why other things like 'malloc' or 'new' are not
>  recommended either?

Real-time means "as fast as possible". Waiting to acquire a lock isn't exactly 
what you would call "fast"...
Waiting for a lock is the same as waiting for the kernels/OSs memory managment 
to allocate some space.

Have fun,

Arnold

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev

Reply via email to