Thread (17 messages) 17 messages, 7 authors, 2015-07-21

Re: [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add mlock flags to enable it

From: Jonathan Corbet <corbet@lwn.net>
Date: 2015-07-10 16:11:45
Also in: linux-api, linux-arch, linux-mips, linux-mm, linuxppc-dev, lkml, sparclinux

On Thu, 9 Jul 2015 14:46:35 -0400
Eric B Munson [off-list ref] wrote:
quoted
One other question...if I call mlock2(MLOCK_ONFAULT) on a range that
already has resident pages, I believe that those pages will not be locked
until they are reclaimed and faulted back in again, right?  I suspect that
could be surprising to users.  
That is the case.  I am looking into what it would take to find only the
present pages in a range and lock them, if that is the behavior that is
preferred I can include it in the updated series.
For whatever my $0.02 is worth, I think that should be done.  Otherwise
the mlock2() interface is essentially nondeterministic; you'll never
really know if a specific page is locked or not.

Thanks,

jon
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help