[LV2] mlock/munlock

David Robillard d at drobilla.net
Wed May 29 08:33:31 PDT 2013

On Wed, 2013-05-29 at 10:09 +0200, hermann meyer wrote:
> Hi
> I wonder what the recommended way for LV2 plugs is? Should plugs use 
> mlock/munlock to lock data into ram which needed during rt-process, or 
> is that contra-productive for the host?
> For example it could make sense to lock up wave-tables or similar data 
> and function calls, to avoid page-faults. But on the other hand it makes 
> no sense when therefore other plugs which didn't use mlock to lock there 
> data, get page-faults.
> any opinions ?

I can't think of any serious problems that mlocking internal
plugin-allocated things would cause.

That said, in practice it probably doesn't matter much in Jack, since
everything is mlocked anyway.  Probably doesn't even matter much in
general since if you're low enough on memory for frequently used things
to get swapped out you're probably screwed anyway.  It shouldn't hurt,


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lv2plug.in/pipermail/devel-lv2plug.in/attachments/20130529/dc52e437/attachment-0002.pgp>

More information about the Devel mailing list