Main index | Section 2 | 日本語 | Options |
#include <sys/mman.h>
The following flags affect the behavior of mlockall():
MCL_CURRENT | |
Lock all pages currently mapped into the process's address space. | |
MCL_FUTURE | 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.
If 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 for mlockall() calls.
The munlockall() call unlocks any locked memory regions in the process address space. Any regions mapped after an munlockall() call will not be locked.
[EINVAL] | |
The flags argument is zero, or includes unimplemented flags. | |
[ENOMEM] | |
Locking the indicated range would exceed either the system or per-process limit for locked memory. | |
[EAGAIN] | |
Some or all of the memory mapped into the process's address space could not be locked when the call was made. | |
[EPERM] | |
The calling process does not have the appropriate privilege to perform the requested operation. | |
MLOCKALL (2) | May 13, 2019 |
Main index | Section 2 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.