Re: [PATCH V3 0/5] Allow user to request memory to be locked on page fault

2015-07-08 Thread Andrew Morton
On Wed, 8 Jul 2015 09:23:02 -0400 Eric B Munson wrote: > > I don't know whether these syscalls should be documented via new > > manpages, or if we should instead add them to the existing > > mlock/munlock/mlockall manpages. Michael, could you please advise? > > > > Thanks for adding the series

Re: [PATCH V3 0/5] Allow user to request memory to be locked on page fault

2015-07-08 Thread Eric B Munson
On Tue, 07 Jul 2015, Andrew Morton wrote: > On Tue, 7 Jul 2015 13:03:38 -0400 Eric B Munson wrote: > > > mlock() allows a user to control page out of program memory, but this > > comes at the cost of faulting in the entire mapping when it is > > allocated. For large mappings where the entire a

Re: [PATCH V3 0/5] Allow user to request memory to be locked on page fault

2015-07-07 Thread Andrew Morton
On Tue, 7 Jul 2015 13:03:38 -0400 Eric B Munson wrote: > mlock() allows a user to control page out of program memory, but this > comes at the cost of faulting in the entire mapping when it is > allocated. For large mappings where the entire area is not necessary > this is not ideal. Instead of

[PATCH V3 0/5] Allow user to request memory to be locked on page fault

2015-07-07 Thread Eric B Munson
mlock() allows a user to control page out of program memory, but this comes at the cost of faulting in the entire mapping when it is allocated. For large mappings where the entire area is not necessary this is not ideal. Instead of forcing all locked pages to be present when they are allocated, t