On Mon, 2010-01-18 at 14:32 +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. Agreed, mlockall() is a very bad interface and should not be used for a plethora of reasons, this being one of them. The thing is, if you cant trust your library to do sane things, then don't use it. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
