lkml.org 
[lkml]   [2015]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 1/3] mm: mmap make MAP_LOCKED really mlock semantic
On Tue, 28 Apr 2015 14:11:49 +0200 Michal Hocko <mhocko@suse.cz> wrote:

> The man page however says
> "
> MAP_LOCKED (since Linux 2.5.37)
> Lock the pages of the mapped region into memory in the manner of
> mlock(2). This flag is ignored in older kernels.
> "

I'm trying to remember why we implemented MAP_LOCKED in the first
place. Was it better than mmap+mlock in some fashion?

afaict we had a #define MAP_LOCKED in the header file but it wasn't
implemented, so we went and wired it up. 13 years ago:
https://lkml.org/lkml/2002/9/18/108


Anyway... the third way of doing this is to use plain old mmap() while
mlockall(MCL_FUTURE) is in force. Has anyone looked at that, checked
that the behaviour is sane and compared it with the mmap+mlock
behaviour, the MAP_LOCKED behaviour and the manpages?




\
 
 \ /
  Last update: 2015-04-29 01:21    [W:0.112 / U:0.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site