summaryrefslogtreecommitdiffstats
path: root/man5/proc_sys_vm.5
diff options
context:
space:
mode:
Diffstat (limited to 'man5/proc_sys_vm.5')
-rw-r--r--man5/proc_sys_vm.533
1 files changed, 17 insertions, 16 deletions
diff --git a/man5/proc_sys_vm.5 b/man5/proc_sys_vm.5
index 17a7dd2ec..d4c19f460 100644
--- a/man5/proc_sys_vm.5
+++ b/man5/proc_sys_vm.5
@@ -31,10 +31,10 @@ Systems running in "overcommit never" mode (i.e., 2 in
.IR /proc/sys/vm/overcommit_memory )
should increase the value in this file to account
for the full virtual memory size of the programs used to recover (e.g.,
-.BR login (1)
-.BR ssh (1),
+.MR login 1
+.MR ssh 1 ,
and
-.BR top (1))
+.MR top 1 )
Otherwise, the superuser may not be able to log in to recover the system.
For example, on x86-64 a suitable value is 131072 (128MiB reserved).
.IP
@@ -85,7 +85,7 @@ echo 3 > /proc/sys/vm/drop_caches
Because writing to this file is a nondestructive operation and dirty objects
are not freeable, the
user should run
-.BR sync (1)
+.MR sync 1
first.
.TP
.IR /proc/sys/vm/sysctl_hugetlb_shm_group " (since Linux 2.6.7)"
@@ -96,10 +96,10 @@ matches this group ID,
then it can make huge-page allocations without holding the
.B CAP_IPC_LOCK
capability; see
-.BR memfd_create (2),
-.BR mmap (2),
+.MR memfd_create 2 ,
+.MR mmap 2 ,
and
-.BR shmget (2).
+.MR shmget 2 .
.TP
.IR /proc/sys/vm/legacy_va_layout " (since Linux 2.6.9)"
.\" The following is from Documentation/filesystems/proc.txt
@@ -140,7 +140,7 @@ signal with
set to
.BR BUS_MCEERR_AO .
Processes can handle this if they want to; see
-.BR sigaction (2)
+.MR sigaction 2
for more details.
.IP
This feature is active only on architectures/platforms with advanced machine
@@ -149,7 +149,7 @@ check handling and depends on the hardware capabilities.
Applications can override the
.I memory_failure_early_kill
setting individually with the
-.BR prctl (2)
+.MR prctl 2
.B PR_MCE_KILL
operation.
.IP
@@ -263,7 +263,7 @@ Values are:
.RE
.IP
In mode 0, calls of
-.BR mmap (2)
+.MR mmap 2
with
.B MAP_NORESERVE
are not checked, and the default check is very weak,
@@ -355,7 +355,8 @@ using memory policies
.RB ( mbind (2)
.BR MPOL_BIND )
or cpusets
-.RB ( cpuset (7))
+\%(\c
+.MR cpuset 7 )
and those nodes reach memory exhaustion status,
one process may be killed by the OOM-killer.
No panic occurs in this case:
@@ -407,14 +408,14 @@ an application requests memory.
.\" cefdca0a86be517bc390fc4541e3674b8e7803b0
This (writable) file exposes a flag that controls whether
unprivileged processes are allowed to employ
-.BR userfaultfd (2).
+.MR userfaultfd 2 .
If this file has the value 1, then unprivileged processes may use
-.BR userfaultfd (2).
+.MR userfaultfd 2 .
If this file has the value 0, then only processes that have the
.B CAP_SYS_PTRACE
capability may employ
-.BR userfaultfd (2).
+.MR userfaultfd 2 .
The default value in this file is 1.
.SH SEE ALSO
-.BR proc (5),
-.BR proc_sys (5)
+.MR proc 5 ,
+.MR proc_sys 5