|MLOCKALL(2)||System Calls Manual||MLOCKALL(2)|
munlockall — lock (unlock)
the address space of a process
Standard C Library (libc, -lc)
system call locks into memory the physical pages associated with the address
space of a process until the address space is unlocked, the process exits,
or execs another program image.
The following flags affect the behavior of
- Lock all pages currently mapped into the process's address space.
- Lock all pages mapped into the process's address space in the future, at the time the mapping is established. Note that this may cause future mappings to fail if those mappings cause resource limits to be exceeded.
Since physical memory is a potentially scarce resource, processes
are limited in how much they can lock down. A single process can lock the
minimum of a system-wide “wired pages” limit
vm.max_user_wired and the per-process
RLIMIT_MEMLOCK resource limit.
security.bsd.unprivileged_mlock is set to 0 these
calls are only available to the super-user. If
vm.old_mlock is set to 1 the per-process
RLIMIT_MEMLOCK resource limit will not be applied
call unlocks any locked memory regions in the process address space. Any
regions mapped after an
munlockall() call will not
A return value of 0 indicates that the call succeeded and all pages in the range have either been locked or unlocked. A return value of -1 indicates an error occurred and the locked status of all pages in the range remains unchanged. In this case, the global location errno is set to indicate the error.
mlockall() will fail if:
- The flags argument is zero, or includes unimplemented flags.
- Locking the indicated range would exceed either the system or per-process limit for locked memory.
- Some or all of the memory mapped into the process's address space could not be locked when the call was made.
- The calling process does not have the appropriate privilege to perform the requested operation.
munlockall() functions are believed to conform to
IEEE Std 1003.1-2001 (“POSIX.1”).
munlockall() functions first appeared in
The per-process and system-wide resource limits of locked memory apply to the amount of virtual memory locked, not the amount of locked physical pages. Hence two distinct locked mappings of the same physical page counts as 2 pages aginst the system limit, and also against the per-process limit if both mappings belong to the same physical map.
|May 13, 2019||Debian|