From: Li Zefan <lizefan@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, 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: [PATCH v6 0/5] memcg, cgroup: kill css id
Date: Mon, 23 Sep 2013 16:55:20 +0800 [thread overview]
Message-ID: <524001F8.6070205@huawei.com> (raw)
Hi Andrew,
The whole patchset has been acked and reviewed by Michal and Tejun.
Could you merge it into mm tree?
===========
This patchset converts memcg to use cgroup->id, and then we remove cgroup
css_id.
As we've removed memcg's own refcnt, converting memcg to use cgroup->id
is very straight-forward.
v6:
- rebased against mmotm 2013-09-20-15-59
- moved cgroup id check from mem_cgroup_css_alloc() to mem_cgroup_css_online()
v5:
- rebased against mmotm 2013-08-07-16-55
v4:
- make cgroup_from_id() inline and check if cgroup_mutex is held.
- add a comment for idr_remove() in cgroup_offline)fn().
v2->v3:
- some minor cleanups suggested by Michal.
- fixed the call to idr_alloc() in cgroup_init() in the first patch.
Li Zefan (5):
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 | 37 --------
kernel/cgroup.c | 248 +------------------------------------------------
mm/memcontrol.c | 66 +++++++------
3 files changed, 41 insertions(+), 310 deletions(-)
--
1.8.0.2
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizefan@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>, 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: [PATCH v6 0/5] memcg, cgroup: kill css id
Date: Mon, 23 Sep 2013 16:55:20 +0800 [thread overview]
Message-ID: <524001F8.6070205@huawei.com> (raw)
Hi Andrew,
The whole patchset has been acked and reviewed by Michal and Tejun.
Could you merge it into mm tree?
===========
This patchset converts memcg to use cgroup->id, and then we remove cgroup
css_id.
As we've removed memcg's own refcnt, converting memcg to use cgroup->id
is very straight-forward.
v6:
- rebased against mmotm 2013-09-20-15-59
- moved cgroup id check from mem_cgroup_css_alloc() to mem_cgroup_css_online()
v5:
- rebased against mmotm 2013-08-07-16-55
v4:
- make cgroup_from_id() inline and check if cgroup_mutex is held.
- add a comment for idr_remove() in cgroup_offline)fn().
v2->v3:
- some minor cleanups suggested by Michal.
- fixed the call to idr_alloc() in cgroup_init() in the first patch.
Li Zefan (5):
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 | 37 --------
kernel/cgroup.c | 248 +------------------------------------------------
mm/memcontrol.c | 66 +++++++------
3 files changed, 41 insertions(+), 310 deletions(-)
--
1.8.0.2
next reply other threads:[~2013-09-23 8:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 8:55 Li Zefan [this message]
2013-09-23 8:55 ` [PATCH v6 0/5] memcg, cgroup: kill css id Li Zefan
2013-09-23 8:55 ` [PATCH v6 1/5] memcg: convert to use cgroup_is_descendant() Li Zefan
2013-09-23 8:55 ` Li Zefan
2013-09-23 8:56 ` [PATCH v6 2/5] memcg: convert to use cgroup id Li Zefan
2013-09-23 8:56 ` Li Zefan
[not found] ` <524001F8.6070205-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
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 ` Li Zefan
2013-09-23 8:56 ` Li Zefan
2013-09-23 8:56 ` [PATCH v6 4/5] memcg: stop using css id Li Zefan
2013-09-23 8:56 ` Li Zefan
2013-09-23 8:56 ` Li Zefan
2013-09-23 8:57 ` [PATCH v6 5/5] cgroup: kill css_id Li Zefan
2013-09-23 8:57 ` Li Zefan
2013-09-23 8:57 ` Li Zefan
2013-09-23 13:08 ` [PATCH v6 0/5] memcg, cgroup: kill css id Tejun Heo
2013-09-23 13:08 ` Tejun Heo
2013-09-23 13:08 ` Tejun Heo
[not found] ` <20130923130816.GH30946-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-09-23 13:12 ` Tejun Heo
2013-09-23 13:12 ` Tejun Heo
2013-09-23 13:12 ` Tejun Heo
2013-09-24 0:32 ` Li Zefan
2013-09-24 0:32 ` Li Zefan
[not found] ` <5240DD83.1070509-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-09-24 0:52 ` Andrew Morton
2013-09-24 0:52 ` Andrew Morton
2013-09-24 0:52 ` Andrew Morton
2013-09-24 1:30 ` Tejun Heo
2013-09-24 1:30 ` Tejun Heo
2013-09-24 1:52 ` Tejun Heo
2013-09-24 1:52 ` Tejun Heo
[not found] ` <20130924015211.GD3482-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-09-24 1:54 ` Stephen Rothwell
2013-09-24 1:54 ` Stephen Rothwell
2013-09-24 1:46 ` Tejun Heo
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=524001F8.6070205@huawei.com \
--to=lizefan@huawei.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.