From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Li Zefan <lizefan@huawei.com>, Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>,
cgroups <cgroups@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v6 0/5] memcg, cgroup: kill css id
Date: Tue, 24 Sep 2013 11:54:20 +1000 [thread overview]
Message-ID: <20130924115420.a69505b10763ef89953698a8@canb.auug.org.au> (raw)
In-Reply-To: <20130924015211.GD3482@htj.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
Hi Tejun,
On Mon, 23 Sep 2013 21:52:11 -0400 Tejun Heo <tj@kernel.org> wrote:
>
> (cc'ing Stephen, hi!)
Hi :-)
> On Mon, Sep 23, 2013 at 09:30:58PM -0400, Tejun Heo wrote:
> >
> > On Mon, Sep 23, 2013 at 05:52:47PM -0700, Andrew Morton wrote:
> > > > I would love to see this patchset go through cgroup tree. The changes to
> > > > memcg is quite small,
> > >
> > > It seems logical to put this in the cgroup tree as that's where most of
> > > the impact occurs.
> >
> > Cool, applying the changes to cgroup/for-3.13.
>
> Stephen, Andrew, cgroup/for-3.13 will cause a minor conflict in
> mm/memcontrol.c with the patch which reverts Michal's reclaim changes.
>
> static void __mem_cgroup_free(struct mem_cgroup *memcg)
> {
> int node;
> size_t size = memcg_size();
>
> <<<<<<< HEAD
> =======
> mem_cgroup_remove_from_trees(memcg);
> free_css_id(&mem_cgroup_subsys, &memcg->css);
>
> >>>>>>> 1fa8f71dfa6e28c89afad7ac71dcb19b8c8da8b7
> for_each_node(node)
> free_mem_cgroup_per_zone_info(memcg, node);
>
> It's a context conflict and just removing free_css_id() call resolves
> it.
>
> static void __mem_cgroup_free(struct mem_cgroup *memcg)
> {
> int node;
> size_t size = memcg_size();
>
> mem_cgroup_remove_from_trees(memcg);
>
> for_each_node(node)
> free_mem_cgroup_per_zone_info(memcg, node);
Thanks for the heads up, I guess I'll see that tomorrow.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-24 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 8:55 Li Zefan
2013-09-23 8:55 ` [PATCH v6 1/5] memcg: convert to use cgroup_is_descendant() Li Zefan
2013-09-23 8:56 ` [PATCH v6 2/5] memcg: convert to use cgroup id Li Zefan
2013-09-23 8:56 ` [PATCH v6 3/5] memcg: fail to create cgroup if the cgroup id is too big Li Zefan
2013-09-23 8:56 ` [PATCH v6 4/5] memcg: stop using css id Li Zefan
2013-09-23 8:57 ` [PATCH v6 5/5] cgroup: kill css_id Li Zefan
2013-09-23 13:08 ` [PATCH v6 0/5] memcg, cgroup: kill css id Tejun Heo
2013-09-23 13:12 ` Tejun Heo
2013-09-24 0:32 ` Li Zefan
2013-09-24 0:52 ` Andrew Morton
2013-09-24 1:30 ` Tejun Heo
2013-09-24 1:52 ` Tejun Heo
2013-09-24 1:54 ` Stephen Rothwell [this message]
2013-09-24 1:46 ` Tejun Heo
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=20130924115420.a69505b10763ef89953698a8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.cz \
--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