From e9a39e76f4397abf0406ecdeb038722221e24d15 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Wed, 26 Apr 2017 10:32:51 -0700 Subject: [PATCH] config-linux: RFC 2119 wording for oomScoreAdj The previous wording hinted at, but did not require, this setting to be implemented via oom_score_adj. With the new wording, when proc is mounted at /proc, the container process can check this value by looking at /proc/self/oom_score_adj. Signed-off-by: W. Trevor King --- config-linux.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/config-linux.md b/config-linux.md index 52c0791cd..b6643aa51 100644 --- a/config-linux.md +++ b/config-linux.md @@ -265,13 +265,13 @@ For more information, see [the memory cgroup man page][cgroup-v1-memory]. #### Set oom_score_adj -`oomScoreAdj` sets heuristic regarding how the process is evaluated by the kernel during memory pressure. -For more information, see [the proc filesystem documentation section 3.1][procfs]. +* **`oomScoreAdj`** *(int, OPTIONAL)* adjusts the oom-killer score in `[pid]/oom_score_adj` for the container process's `[pid]` in a [proc pseudo-filesystem][procfs]. + If `oomScoreAdj` is set, the runtime MUST set `oom_score_adj` to the given value. + If `oomScoreAdj` is not set, the runtime MUST NOT change the value of `oom_score_adj`. + This is a kernel/system level setting, where as `disableOOMKiller` is scoped for a memory cgroup. For more information on how these two settings work together, see [the memory cgroup documentation section 10. OOM Contol][cgroup-v1-memory]. -* **`oomScoreAdj`** *(int, OPTIONAL)* - adjust the oom-killer score - ###### Example ```json