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
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
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
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
4 matches
Mail list logo