[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YDkGwN2rQ5lI6LnE@chrisdown.name>
Date: Fri, 26 Feb 2021 14:33:36 +0000
From: Chris Down <chris@...isdown.name>
To: Yang Shi <shy828301@...il.com>
Cc: hannes@...xchg.org, mhocko@...e.com, guro@...com,
shakeelb@...gle.com, akpm@...ux-foundation.org, corbet@....net,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] doc: memcontrol: add description for oom_kill
Yang Shi writes:
>When debugging an oom issue, I found the oom_kill counter of memcg is
>confusing. At the first glance without checking document, I thought it
>just counts for memcg oom, but it turns out it counts both global and
>memcg oom.
>
>The cgroup v2 documents it, but the description is missed for cgroup v1.
>
>Signed-off-by: Yang Shi <shy828301@...il.com>
Thanks.
Acked-by: Chris Down <chris@...isdown.name>
>---
> Documentation/admin-guide/cgroup-v1/memory.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
>diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
>index 0936412e044e..44d5429636e2 100644
>--- a/Documentation/admin-guide/cgroup-v1/memory.rst
>+++ b/Documentation/admin-guide/cgroup-v1/memory.rst
>@@ -851,6 +851,9 @@ At reading, current status of OOM is shown.
> (if 1, oom-killer is disabled)
> - under_oom 0 or 1
> (if 1, the memory cgroup is under OOM, tasks may be stopped.)
>+ - oom_kill integer counter
>+ The number of processes belonging to this cgroup killed by any
>+ kind of OOM killer.
>
> 11. Memory Pressure
> ===================
>--
>2.26.2
>
>
Powered by blists - more mailing lists