From: Michal Hocko <mhocko@suse.cz>
To: Li Zefan <lizefan@huawei.com>
Cc: Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Glauber Costa <glommer@parallels.com>,
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
Subject: Re: [PATCH v2 0/8] memcg, cgroup: kill css_id
Date: Wed, 24 Jul 2013 16:32:14 +0200 [thread overview]
Message-ID: <20130724143214.GL2540@dhcp22.suse.cz> (raw)
In-Reply-To: <51EFA554.6080801@huawei.com>
On Wed 24-07-13 17:58:44, Li Zefan wrote:
> This patchset converts memcg to use cgroup->id, and then we can remove
> cgroup css_id.
>
> As we've removed memcg's own refcnt, converting memcg to use cgroup->id
> is very straight-forward.
>
> The patchset is based on Tejun's cgroup tree.
Does it depend on any particular patches? I am asking because I would
need to cherry pick those and apply them into my -mm git tree before
these.
> Li Zefan (8):
> cgroup: convert cgroup_ida to cgroup_idr
> cgroup: document how cgroup IDs are assigned
> cgroup: implement cgroup_from_id()
> memcg: convert to use cgroup_is_descendant()
> memcg: convert to use cgroup id
> memcg: fail to create cgroup if the cgroup id is too big
> memcg: stop using css id
> cgroup: kill css_id
> --
> include/linux/cgroup.h | 49 ++-------
> kernel/cgroup.c | 308 ++++++++-----------------------------------------------
> mm/memcontrol.c | 59 ++++++-----
> 3 files changed, 90 insertions(+), 326 deletions(-)
--
Michal Hocko
SUSE Labs
--
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:[~2013-07-24 14:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 9:58 [PATCH v2 0/8] memcg, cgroup: kill css_id Li Zefan
2013-07-24 9:59 ` [PATCH v2 1/8] cgroup: convert cgroup_ida to cgroup_idr Li Zefan
2013-07-24 14:07 ` Michal Hocko
2013-07-25 1:08 ` Li Zefan
2013-07-24 9:59 ` [PATCH v2 2/8] cgroup: document how cgroup IDs are assigned Li Zefan
2013-07-24 14:07 ` Michal Hocko
2013-07-24 10:00 ` [PATCH v2 3/8] cgroup: implement cgroup_from_id() Li Zefan
2013-07-24 14:10 ` Michal Hocko
2013-07-24 10:01 ` [PATCH v2 4/8] memcg: convert to use cgroup_is_descendant() Li Zefan
2013-07-24 14:20 ` Michal Hocko
2013-07-24 10:01 ` [PATCH v2 5/8] memcg: convert to use cgroup id Li Zefan
2013-07-24 14:25 ` Michal Hocko
2013-07-24 10:02 ` [PATCH v2 6/8] memcg: fail to create cgroup if the cgroup id is too big Li Zefan
2013-07-24 14:27 ` Michal Hocko
2013-07-24 10:03 ` [PATCH v2 7/8] memcg: stop using css id Li Zefan
2013-07-24 14:30 ` Michal Hocko
2013-07-24 10:03 ` [PATCH v2 8/8] cgroup: kill css_id Li Zefan
2013-07-24 14:31 ` Michal Hocko
2013-07-24 14:32 ` Michal Hocko [this message]
2013-07-24 16:14 ` [PATCH v2 0/8] memcg, " Tejun Heo
2013-07-25 7:40 ` Michal Hocko
2013-07-25 0:59 ` Li Zefan
2013-07-25 7:41 ` 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=20130724143214.GL2540@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=glommer@parallels.com \
--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=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).