> Using sys_mlock(), we're able to lock the memory buffer down, but this > is not an ideal solution. it most certainly isn't; since the user app can just call munlock on the same memory from another thread... in parallel. > What I'd like to do is create a new VMA for > just the memory buffer, and then lock that VMA. Locking the VMA is what > really locks the buffer. oh? and what stops the other thread from mucking with the VMA ?
Attachment:
signature.asc
Description: This is a digitally signed message part