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

From	Jonathan Corbet <corbet@lwn.net>
Newsgroups	linux.kernel
Subject	Re: [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add mlock flags to enable it
Date	2015-07-10 18:20 +0200
Message-ID	<pKJbQ-8ea-13@gated-at.bofh.it> (permalink)
References	(1 earlier) <pJEHh-8rS-11@gated-at.bofh.it> <pK3cC-6Qv-17@gated-at.bofh.it> <pK4im-7EX-11@gated-at.bofh.it> <pK4V4-88w-25@gated-at.bofh.it> <pKp3r-3HJ-5@gated-at.bofh.it>
Organization	LWN.net

Show all headers | View raw

On Thu, 9 Jul 2015 14:46:35 -0400
Eric B Munson <emunson@akamai.com> wrote:

> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add  mlock flags to enable it Jonathan Corbet <corbet@lwn.net> - 2015-07-10 18:20 +0200
  Re: [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add mlock  flags to enable it Eric B Munson <emunson@akamai.com> - 2015-07-10 18:30 +0200

csiph-web