Messages in this thread Patch in this message |  | | From | Michal Hocko <> | Subject | [PATCH 2/2] doc, mm: clarify /proc/<pid>/oom_score value range | Date | Thu, 9 Jul 2020 08:26:03 +0200 |
| |
From: Michal Hocko <mhocko@suse.com>
The exported value includes oom_score_adj so the range is no [0, 1000] as described in the previous section but rather [0, 2000]. Mention that fact explicitly.
Signed-off-by: Michal Hocko <mhocko@suse.com> --- Documentation/filesystems/proc.rst | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst index 8e3b5dffcfa8..78a0dec323a3 100644 --- a/Documentation/filesystems/proc.rst +++ b/Documentation/filesystems/proc.rst @@ -1673,6 +1673,9 @@ requires CAP_SYS_RESOURCE. 3.2 /proc/<pid>/oom_score - Display current oom-killer score ------------------------------------------------------------- +Please note that the exported value includes oom_score_adj so it is effectively +in range [0,2000]. + This file can be used to check the current score used by the oom-killer is for any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which process should be killed in an out-of-memory situation. -- 2.27.0
|  |