From: David Rientjes <rientjes@google.com>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Guschin <guroan@gmail.com>
Subject: Re: [PATCH v2] mm/oom_kill: count global and memory cgroup oom kills
Date: Mon, 29 May 2017 21:29:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1705292129170.9353@chino.kir.corp.google.com> (raw)
In-Reply-To: <149570810989.203600.9492483715840752937.stgit@buzz>
On Thu, 25 May 2017, Konstantin Khlebnikov wrote:
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 04c9143a8625..dd30a045ef5b 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -876,6 +876,11 @@ static void oom_kill_process(struct oom_control *oc, const char *message)
> /* Get a reference to safely compare mm after task_unlock(victim) */
> mm = victim->mm;
> mmgrab(mm);
> +
> + /* Raise event before sending signal: reaper must see this */
How is the oom reaper involved here?
> + count_vm_event(OOM_KILL);
> + mem_cgroup_count_vm_event(mm, OOM_KILL);
> +
> /*
> * We should send SIGKILL before setting TIF_MEMDIE in order to prevent
> * the OOM victim from depleting the memory reserves from the user
--
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-30 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 10:28 Konstantin Khlebnikov
2017-05-30 4:29 ` David Rientjes [this message]
2017-05-30 4:51 ` Konstantin Khlebnikov
2017-06-05 8:50 ` Michal Hocko
2017-06-05 14:27 ` Konstantin Khlebnikov
2017-06-08 9:44 ` Michal Hocko
2017-09-13 4:51 ` PINTU KUMAR
2017-09-13 7:35 ` Konstantin Khlebnikov
2017-09-13 14:33 ` Pintu Kumar
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.1705292129170.9353@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=guroan@gmail.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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