From: David Rientjes <rientjes@google.com>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: Roman Guschin <guroan@gmail.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>,
Michal Hocko <mhocko@kernel.org>,
hannes@cmpxchg.org
Subject: Re: [PATCH] mm/oom_kill: count global and memory cgroup oom kills
Date: Tue, 23 May 2017 00:49:30 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1705230044590.50796@chino.kir.corp.google.com> (raw)
In-Reply-To: <ecd4a7ea-06c0-f549-a1bf-6d2d3c0af719@yandex-team.ru>
On Mon, 22 May 2017, Konstantin Khlebnikov wrote:
> Nope, they are different. I think we should rephase documentation somehow
>
> low - count of reclaims below low level
> high - count of post-allocation reclaims above high level
> max - count of direct reclaims
> oom - count of failed direct reclaims
> oom_kill - count of oom killer invocations and killed processes
>
In our kernel, we've maintained counts of oom kills per memcg for years as
part of memory.oom_control for memcg v1, but we've also found it helpful
to complement that with another count that specifies the number of
processes oom killed that were attached to that exact memcg.
In your patch, oom_kill in memory.oom_control specifies that number of oom
events that resulted in an oom kill of a process from that hierarchy, but
not the number of processes killed from a specific memcg (the difference
between oc->memcg and mem_cgroup_from_task(victim)). Not sure if you
would also find it helpful.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-23 7:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 14:22 Konstantin Khlebnikov
2017-05-19 14:32 ` Michal Hocko
2017-05-19 16:34 ` Roman Guschin
2017-05-22 9:11 ` Konstantin Khlebnikov
2017-05-22 18:05 ` Roman Guschin
2017-05-23 7:49 ` David Rientjes [this message]
2017-05-23 10:32 ` Konstantin Khlebnikov
2017-05-24 20:43 ` David Rientjes
2017-05-25 8:44 ` Konstantin Khlebnikov
2017-05-23 7:27 ` Michal Hocko
2017-05-23 11:05 ` Konstantin Khlebnikov
2017-05-23 11:29 ` Tetsuo Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.10.1705230044590.50796@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guroan@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox