From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"menage@google.com" <menage@google.com>
Subject: [RFC][PATCH 0/4] cgroup ID and css refcnt change and memcg hierarchy (2008/12/05)
Date: Fri, 5 Dec 2008 17:26:42 +0900 [thread overview]
Message-ID: <20081205172642.565661b1.kamezawa.hiroyu@jp.fujitsu.com> (raw)
This is a patch set onto mmotm-2.6.28-Dec30.
Still RFC. I'm considering whether I can make this simpler....
Major changes from previous one
- css->refcnt is unified.
I think distributed refcnt is a crazy idea...
- applied comments to previous version.
- OOM Kill handler is fixed. (this was broken by hierarchy)
I may not be able to reply quickly in weekend, sorry.
After this, memcg's hierarchical reclaim will be
==
static struct mem_cgroup *
mem_cgroup_select_victim(struct mem_cgroup *root_mem)
{
struct cgroup *cgroup, *root_cgroup;
struct mem_cgroup *ret;
int nextid, rootid, depth, found;
root_cgroup = root_mem->css.cgroup;
rootid = cgroup_id(root_cgroup);
depth = cgroup_depth(root_cgroup);
found = 0;
rcu_read_lock();
if (!root_mem->use_hierarchy) {
spin_lock(&root_mem->reclaim_param_lock);
root_mem->scan_age++;
spin_unlock(&root_mem->reclaim_param_lock);
css_get(&root_mem->css);
ret = root_mem;
}
while (!ret) {
/* ID:0 is not used by cgroup-id */
nextid = root_mem->last_scanned_child + 1;
cgroup = cgroup_get_next(nextid, rootid, depth, &found);
if (cgroup) {
spin_lock(&root_mem->reclaim_param_lock);
root_mem->last_scanned_child = found;
spin_unlock(&root_mem->reclaim_param_lock);
ret = mem_cgroup_from_cont(cgroup);
if (!css_tryget(&ret->css))
ret = NULL;
} else {
spin_lock(&root_mem->reclaim_param_lock);
root_mem->scan_age++;
root_mem->last_scanned_child = 0;
spin_unlock(&root_mem->reclaim_param_lock);
}
}
rcu_read_unlock();
return ret;
}
/*
* root_mem is the original ancestor that we've been reclaim from.
* root_mem cannot be freed while walking because there are children.
*/
static int mem_cgroup_hierarchical_reclaim(struct mem_cgroup *root_mem,
gfp_t gfp_mask, bool noswap)
{
struct mem_cgroup *victim;
unsigned long start_age;
int ret = 0;
int total = 0;
start_age = root_mem->scan_age;
/* allows visit twice (under this memcg, ->scan_age is shared.) */
while (time_after((start_age + 2UL), root_mem->scan_age)) {
victim = mem_cgroup_select_victim(root_mem);
ret = try_to_free_mem_cgroup_pages(victim,
gfp_mask, noswap, get_swappiness(victim));
css_put(&victim->css);
if (mem_cgroup_check_under_limit(root_mem))
return 1;
total += ret;
}
ret = total;
if (mem_cgroup_check_under_limit(root_mem))
ret = 1;
return ret;
}
==
This can be reused for soft-limit or something fancy featrues.
Regards,
-Kame
--
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 reply other threads:[~2008-12-05 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 8:26 KAMEZAWA Hiroyuki [this message]
2008-12-05 8:28 ` [RFC][PATCH 1/4] New css->refcnt implementation KAMEZAWA Hiroyuki
2008-12-05 9:39 ` Paul Menage
2008-12-05 11:24 ` KAMEZAWA Hiroyuki
2008-12-10 9:00 ` Paul Menage
2008-12-10 10:23 ` KAMEZAWA Hiroyuki
2008-12-05 8:29 ` [RFC][PATCH 2/4] cgroup ID KAMEZAWA Hiroyuki
2008-12-05 11:11 ` Paul Menage
2008-12-05 11:50 ` KAMEZAWA Hiroyuki
2008-12-05 8:31 ` [RFC][PATCH 3/4] memcg: hierachical reclaim KAMEZAWA Hiroyuki
2008-12-05 8:32 ` [RFC][PATCH 4/4] fix oom kill under hierarchy KAMEZAWA Hiroyuki
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=20081205172642.565661b1.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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