On 10/15/2018 10:51 PM, Fons Adriaensen wrote:
Hello all,
A simple question: does libjack (try to) lock client memory ?
There is no simple answer, except "depends".
jack2: no.
jack1: yes, for client threads. jack1 also calls mlockall() and has a
blacklist of system-wide libs/path to not lock [1]. You can however
disable it with an option at compile and runtime.
Both jack1 and jack2's libjack's ringbuffer implementation has an API
jack_ringbuffer_mlock(), but that needs an explicit call.
Cheers!
robin
[1]
https://github.com/jackaudio/jack1/blob/master/libjack/unlock.c