[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180308154501.a42bb22af0da6ccd727773c8@linux-foundation.org>
Date: Thu, 8 Mar 2018 15:45:01 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Shakeel Butt <shakeelb@...gle.com>
Cc: Roman Gushchin <guro@...com>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Michal Hocko <mhocko@...nel.org>,
Greg Thelen <gthelen@...gle.com>,
Johannes Weiner <hannes@...xchg.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
David Rientjes <rientjes@...gle.com>
Subject: Re: [PATCH] mm: memcg: expose mem_cgroup_put API
On Wed, 7 Mar 2018 18:48:50 -0800 Shakeel Butt <shakeelb@...gle.com> wrote:
> This patch exports mem_cgroup_put API to put the refcnt of the memory
> cgroup.
OK, I remember now. This is intended to make
fs-fsnotify-account-fsnotify-metadata-to-kmemcg.patch independent of
mm-oom-cgroup-aware-oom-killer.patch by extracting mem_cgroup_put()
from mm-oom-cgroup-aware-oom-killer.patch.
However it will not permit me to stage
fs-fsnotify-account-fsnotify-metadata-to-kmemcg.patch ahead of
mm-oom-cgroup-aware-oom-killer.patch because there are quite a lot of
syntactic clashes.
I can resolve those if needed, but am keenly hoping that the
mm-oom-cgroup-aware-oom-killer.patch issues are resolved soon so there
isn't a need to do this.
Powered by blists - more mailing lists