LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

mlock.2: /proc/PID/status VmLck shows how much memory a process has locked 

After a note from Tom Swigg, it seems sensible mention VmLck here.

Reported-by: Tom Swigg <swiggtc@lsbu.ac.uk>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2010-03-05 03:55:42 +01:00
parent 84a589d224
commit ec8bcce2a8
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
man2/mlock.2
View File

@ -24,7 +24,7 @@
.\" Software Foundation, Inc., 59 Temple Place, Suite 330,
.\" Boston, MA 02111, USA.
.\"
.TH MLOCK 2 2008-09-25 "Linux" "Linux Programmer's Manual"
.TH MLOCK 2 2010-03-05 "Linux" "Linux Programmer's Manual"
.SH NAME
mlock, munlock, mlockall, munlockall \- lock and unlock memory
.SH SYNOPSIS
@ -283,6 +283,19 @@ down to the nearest page boundary.
However, POSIX.1-2001 allows an implementation to require that
.I addr
is page aligned, so portable applications should ensure this.
The
.I VmLck
field of the Linux-specific
.I /proc/PID/status
file shows how many kilobytes of memory the calling process has locked using
.BR mlock (),
.BR mlockall (),
.BR shmctl (2)
.BR SHM_LOCK ,
and
.BR mmap (2)
.BR MAP_LOCKED .
.SS "Limits and permissions"
In Linux 2.6.8 and earlier,
a process must be privileged
@ -326,4 +339,5 @@ resource limit is encountered.
.BR setrlimit (2),
.BR shmctl (2),
.BR sysconf (3),
.BR proc (5),
.BR capabilities (7)