Differences

This shows you the differences between two versions of the page.

--- proc:out_of_memory_killer_score [2017/04/06 14:50] – peter
+++ proc:out_of_memory_killer_score [2020/07/15 09:30] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 These file can be used to adjust the badness heuristic used to select which process gets killed in out of memory conditions.
+<WRAP info>
+**NOTICE**: **/proc/<pid>/oom_adj** is deprecated and will be removed, please see Documentation/feature-removal-schedule.txt.
+</WRAP>
 The badness heuristic assigns a value to each candidate task ranging from 0 (never kill) to 1000 (always kill) to determine which process is targeted.  The units are roughly a proportion along that range of allowed memory the process may allocate from based on an estimation of its current memory and swap use.  For example, if a task is using all allowed memory, its badness score will be 1000.  If it is using half of its allowed memory, its score will be 500.
@@ Line 22: / Line 26: @@
 <WRAP info>
-**NOTICE**: **/proc/<pid>/oom_adj** is deprecated and will be removed, please see Documentation/feature-removal-schedule.txt.
-</WRAP>
 **Caveat**:  When a parent task is selected, the oom killer will sacrifice any first generation children with separate address spaces instead, if possible.  This avoids servers and important system daemons from being killed and loses the minimal amount of work.
+</WRAP>