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

Document /proc/sys/vm/oom_kill_allocating_task (new in Linux 2.6.24).

This commit is contained in:
Michael Kerrisk 2008-07-15 08:48:01 +00:00
parent fb8e1d1b2a
commit e10120df66
1 changed files with 24 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
man5/proc.5
View File

@ -2366,9 +2366,30 @@ first.
.TP
.IR /proc/sys/vm/legacy_va_layout " (since Linux 2.6.9)"
.\" The following is from Documentation/filesystems/proc.txt
If non-zero, this disable the new 32-bit memory-mapping layout;
If non-zero, this disables the new 32-bit memory-mapping layout;
the kernel will use the legacy (2.4) layout for all processes.
.TP
.IR /proc/sys/vm/oom_kill_allocating_task " (since Linux 2.6.24)"
.\" The following is from Documentation/sysctl/vm.txt
This enables or disables killing the OOM-triggering task in
out-of-memory situations.
If this is set to zero, the OOM killer will scan through the entire
tasklist and select a task based on heuristics to kill.
This normally selects a rogue memory-hogging task that
frees up a large amount of memory when killed.
If this is set to non-zero, the OOM killer simply kills the task that
triggered the out-of-memory condition.
This avoids a possibly expensive tasklist scan.
If
.I /proc/sys/vm/panic_on_oom
is non-zero, it takes precedence over whatever value is used in
.IR /proc/sys/vm/oom_kill_allocating_task .
The default value is 0.
.TP
.I /proc/sys/vm/overcommit_memory
This file contains the kernel virtual memory accounting mode.
Values are:
@ -2385,7 +2406,8 @@ In mode 0, calls of
.BR mmap (2)
with
.B MAP_NORESERVE
set are not checked, and the default check is very weak,
are not checked, and the default check is very weak,
leading to the risk of getting a process "OOM-killed".
Under Linux 2.4 any non-zero value implies mode 1.
In mode 2 (available since Linux 2.6), the total virtual address space