Re: [Jack-Devel] Notifications timing

PrevNext  Index
DateMon, 17 Nov 2014 23:10:05 -0500
From Paul Davis <[hidden] at linuxaudiosystems dot com>
To"Tim E. Real" <[hidden] at rogers dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToTim E. Real [Jack-Devel] Notifications timing
Follow-UpTim E. Real Re: [Jack-Devel] Notifications timing
On Mon, Nov 17, 2014 at 11:04 PM, Tim E. Real <[hidden]> wrote:

> Our app uses inter-thread messaging to safely time, to the RT thread,
>  critical modifications, instead of using say non-blocking atomic-safe
>  lists and so on.
>
> I read Jack1 notifies the client from the RT thread, and Jack2 uses a
>  separate notification thread.
>
> So it seems with Jack1, say inside a port connect callback, we /could/
>  directly modify our local structures (routing lists) which our process
>  callback depends on, without delay and safe and since it's all done
>  in the same thread.
>

Your understanding there is correct.


>
> But with Jack2, what is the situation?
>


I'll leave that to someone else, since I've so often gotten my descriptions
of Jack2 incorrect.
PrevNext  Index

1416283813.20120_0.ltw:2, <CAFa_cK=WoefA-NerWc+5vBMMRQ+1ihUOJ+KwQojWVCwiJBQKxw at mail dot gmail dot com>