diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-01-16 14:57:48 +1300 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-01-16 16:36:19 +1300 |
| commit | b017f51b94af908013e977df60f3038f075e487d (patch) | |
| tree | e18f259f74685a778d9c1a4f9f22b57a1fd1e65f /man5 | |
| parent | ae8962dc545328bef0690a01835e364f37a9eebb (diff) | |
| download | man-pages-b017f51b94af908013e977df60f3038f075e487d.tar.gz | |
proc.5: Add some detail on overcommit_memory value 1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man5')
| -rw-r--r-- | man5/proc.5 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/man5/proc.5 b/man5/proc.5 index 7c67d8898c..eebebaeef4 100644 --- a/man5/proc.5 +++ b/man5/proc.5 @@ -5085,6 +5085,11 @@ with .B MAP_NORESERVE are not checked, and the default check is very weak, leading to the risk of getting a process "OOM-killed". + +In mode 1, the kernel pretends there is always enough memory, +until memory actually runs out. +One use case for this mode is scientific computing applications +that employ large sparse arrays. In Linux kernel versions before 2.6.0, any nonzero value implies mode 1. In mode 2 (available since Linux 2.6), the total virtual address space |