This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Support for Intel X1000


Going to prototype first with LD_PRELOAD to make sure I cover all the
bases.

Ray K

On Tue, 2015-05-26 at 14:48 -0400, dalias@libc.org wrote:
> On Tue, May 26, 2015 at 04:32:26PM +0000, Kinsella, Ray wrote:
> > > Is there any known way to change this behavior and eliminate the CoW?
> > 
> > Apologies - to answer my own question ...
> > 
> > "Memory locks are not inherited by a child created via fork(2) and are
> > automatically removed (unlocked) during an execve(2) or when the process
> > terminates. The mlockall() MCL_FUTURE setting is not inherited by a
> > child created via fork(2) and is cleared during an execve(2)."
> > 
> > mlockall(MCL_CURRENT) after the fork,  triggers the CoW upfront.
> 
> Excellent. In a kernel-based workaround, the kernel would enforce
> adding the mlockall at fork time, and then running arbitrary binaries
> would be safe.
> 
> Rich


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]