From: Johannes Weiner <hannes@cmpxchg.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Roman Gushchin <guro@fb.com>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Tejun Heo <tj@kernel.org>,
kernel-team@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm, oom: introduce memory.oom.group
Date: Wed, 1 Aug 2018 13:48:14 -0400 [thread overview]
Message-ID: <20180801174814.GC11386@cmpxchg.org> (raw)
In-Reply-To: <20180801055503.GB16767@dhcp22.suse.cz>
On Wed, Aug 01, 2018 at 07:55:03AM +0200, Michal Hocko wrote:
> On Tue 31-07-18 18:14:48, Roman Gushchin wrote:
> > On Tue, Jul 31, 2018 at 11:07:00AM +0200, Michal Hocko wrote:
> > > On Mon 30-07-18 11:01:00, Roman Gushchin wrote:
> > > > +struct mem_cgroup *mem_cgroup_get_oom_group(struct task_struct *victim,
> > > > + struct mem_cgroup *oom_domain)
> > > > +{
> > > > + struct mem_cgroup *oom_group = NULL;
> > > > + struct mem_cgroup *memcg;
> > > > +
> > > > + if (!cgroup_subsys_on_dfl(memory_cgrp_subsys))
> > > > + return NULL;
> > > > +
> > > > + if (!oom_domain)
> > > > + oom_domain = root_mem_cgroup;
> > > > +
> > > > + rcu_read_lock();
> > > > +
> > > > + memcg = mem_cgroup_from_task(victim);
> > > > + if (!memcg || memcg == root_mem_cgroup)
> > > > + goto out;
> > >
> > > When can we have memcg == NULL? victim should be always non-NULL.
> > > Also why do you need to special case the root_mem_cgroup here. The loop
> > > below should handle that just fine no?
> >
> > Idk, I prefer to keep an explicit root_mem_cgroup check,
> > rather than traversing the tree and relying on an inability
> > to set oom_group on the root.
>
> I will not insist but this just makes the code harder to read.
Just FYI, I'd prefer the explicit check. The loop would do the right
thing, but it's a little too implicit and subtle for my taste...
next prev parent reply other threads:[~2018-08-01 17:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 18:00 [PATCH 0/3] introduce memory.oom.group Roman Gushchin
2018-07-30 18:00 ` [PATCH 1/3] mm: introduce mem_cgroup_put() helper Roman Gushchin
2018-07-31 8:45 ` Michal Hocko
2018-07-31 14:58 ` Shakeel Butt
2018-08-01 5:53 ` Michal Hocko
2018-08-01 17:31 ` Johannes Weiner
2018-07-30 18:00 ` [PATCH 2/3] mm, oom: refactor oom_kill_process() Roman Gushchin
2018-08-01 17:32 ` Johannes Weiner
2018-07-30 18:01 ` [PATCH 3/3] mm, oom: introduce memory.oom.group Roman Gushchin
2018-07-31 9:07 ` Michal Hocko
2018-08-01 1:14 ` Roman Gushchin
2018-08-01 5:55 ` Michal Hocko
2018-08-01 17:48 ` Johannes Weiner [this message]
2018-08-01 17:50 ` Johannes Weiner
2018-07-31 1:49 ` [PATCH 0/3] " David Rientjes
2018-07-31 15:54 ` Johannes Weiner
2018-07-31 23:51 ` Roman Gushchin
2018-08-01 21:51 ` David Rientjes
2018-08-01 22:47 ` Roman Gushchin
2018-08-06 21:34 ` David Rientjes
2018-08-07 0:30 ` Roman Gushchin
2018-08-07 22:34 ` David Rientjes
2018-08-08 10:59 ` Michal Hocko
2018-08-09 20:10 ` David Rientjes
2018-08-10 7:03 ` Michal Hocko
2018-08-19 23:26 ` cgroup aware oom killer (was Re: [PATCH 0/3] introduce memory.oom.group) David Rientjes
2018-08-20 19:05 ` Roman Gushchin
2018-08-02 8:00 ` [PATCH 0/3] introduce memory.oom.group Michal Hocko
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=20180801174814.GC11386@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rientjes@google.com \
--cc=tj@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).