Messages in this thread | | | Date | Mon, 18 Jan 2010 16:35:16 +0200 | From | Gleb Natapov <> | Subject | Re: [PATCH v6] add MAP_UNLOCKED mmap flag |
| |
On Mon, Jan 18, 2010 at 02:32:32PM +0000, Alan Cox wrote: > > this kind of control. As of use of mlockall(MCL_FUTURE) how can I make > > sure that all memory allocated behind my application's back (by dynamic > > linker, libraries, stack) will be locked otherwise? > > If you add this flag you can't do that anyway - some library will > helpfully start up using it and then you are completely stuffed or will > be back in two or three years adding MLOCKALL_ALWAYS. > Libraries can do many other bad things. They can do mlockall(0) today too and this is not the reason to ditch mlockall(). I don't expect libc will do that though.
-- Gleb.
| |