From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"menage@google.com" <menage@google.com>
Subject: Re: [RFC][PATCH 3/4] memcg: fix OOM KILL under hierarchy
Date: Tue, 13 Jan 2009 16:33:12 +0800 [thread overview]
Message-ID: <496C51C8.5040900@cn.fujitsu.com> (raw)
In-Reply-To: <20090108183207.26d88794.kamezawa.hiroyu@jp.fujitsu.com>
> -int task_in_mem_cgroup(struct task_struct *task, const struct mem_cgroup *mem)
> +static int
> +mm_match_cgroup_hierarchy(struct mm_struct *mm, struct mem_cgroup *mem)
> +{
> + struct mem_cgroup *curr;
> + int ret;
> +
> + if (!mm)
> + return 0;
> + rcu_read_lock();
> + curr = mem_cgroup_from_task(mm->owner);
curr can be NULL ?
> + if (mem->use_hierarchy)
> + ret = css_is_ancestor(&curr->css, &mem->css);
> + else
> + ret = (curr == mem);
> + rcu_read_unlock();
> + return ret;
> +}
> +
...
> +void mem_cgroup_update_oom_jiffies(struct mem_cgroup *mem)
> +{
> + struct mem_cgroup *cur;
> + struct cgroup_subsys_state *css;
> + int id, found;
> +
> + if (!mem->use_hierarchy) {
> + mem->last_oom_jiffies = jiffies;
> + return;
> + }
> +
> + id = 0;
> + rcu_read_lock();
> + while (1) {
> + css = css_get_next(&mem_cgroup_subsys, id, &mem->css, &found);
> + if (!css)
> + break;
> + if (css_tryget(css)) {
> + cur = container_of(css, struct mem_cgroup, css);
> + cur->last_oom_jiffies = jiffies;
> + css_put(css);
> + }
> + id = found + 1;
> + }
> + rcu_read_unlock();
> + return;
redundant "return"
> +}
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"menage@google.com" <menage@google.com>
Subject: Re: [RFC][PATCH 3/4] memcg: fix OOM KILL under hierarchy
Date: Tue, 13 Jan 2009 16:33:12 +0800 [thread overview]
Message-ID: <496C51C8.5040900@cn.fujitsu.com> (raw)
In-Reply-To: <20090108183207.26d88794.kamezawa.hiroyu@jp.fujitsu.com>
> -int task_in_mem_cgroup(struct task_struct *task, const struct mem_cgroup *mem)
> +static int
> +mm_match_cgroup_hierarchy(struct mm_struct *mm, struct mem_cgroup *mem)
> +{
> + struct mem_cgroup *curr;
> + int ret;
> +
> + if (!mm)
> + return 0;
> + rcu_read_lock();
> + curr = mem_cgroup_from_task(mm->owner);
curr can be NULL ?
> + if (mem->use_hierarchy)
> + ret = css_is_ancestor(&curr->css, &mem->css);
> + else
> + ret = (curr == mem);
> + rcu_read_unlock();
> + return ret;
> +}
> +
...
> +void mem_cgroup_update_oom_jiffies(struct mem_cgroup *mem)
> +{
> + struct mem_cgroup *cur;
> + struct cgroup_subsys_state *css;
> + int id, found;
> +
> + if (!mem->use_hierarchy) {
> + mem->last_oom_jiffies = jiffies;
> + return;
> + }
> +
> + id = 0;
> + rcu_read_lock();
> + while (1) {
> + css = css_get_next(&mem_cgroup_subsys, id, &mem->css, &found);
> + if (!css)
> + break;
> + if (css_tryget(css)) {
> + cur = container_of(css, struct mem_cgroup, css);
> + cur->last_oom_jiffies = jiffies;
> + css_put(css);
> + }
> + id = found + 1;
> + }
> + rcu_read_unlock();
> + return;
redundant "return"
> +}
--
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:[~2009-01-13 8:34 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 9:25 [RFC][PATCH] cgroup and memcg updates 20090108 KAMEZAWA Hiroyuki
2009-01-08 9:25 ` KAMEZAWA Hiroyuki
2009-01-08 9:28 ` [RFC][PATCH 1/4] cgroup: support per cgroup subsys state ID (CSS ID) KAMEZAWA Hiroyuki
2009-01-08 9:28 ` KAMEZAWA Hiroyuki
2009-01-09 3:59 ` Li Zefan
2009-01-09 3:59 ` Li Zefan
2009-01-09 4:24 ` KAMEZAWA Hiroyuki
2009-01-09 4:24 ` KAMEZAWA Hiroyuki
2009-01-10 0:23 ` Paul Menage
2009-01-10 0:23 ` Paul Menage
2009-01-10 0:49 ` KAMEZAWA Hiroyuki
2009-01-10 0:49 ` KAMEZAWA Hiroyuki
2009-01-12 7:21 ` Balbir Singh
2009-01-12 7:21 ` Balbir Singh
2009-01-15 6:12 ` KAMEZAWA Hiroyuki
2009-01-15 6:12 ` KAMEZAWA Hiroyuki
2009-01-13 7:40 ` Li Zefan
2009-01-13 7:40 ` Li Zefan
2009-01-13 9:22 ` KAMEZAWA Hiroyuki
2009-01-13 9:22 ` KAMEZAWA Hiroyuki
2009-01-08 9:30 ` [RFC][PATCH 2/4] memcg: use CSS ID in memcg KAMEZAWA Hiroyuki
2009-01-08 9:30 ` KAMEZAWA Hiroyuki
2009-01-12 12:14 ` Balbir Singh
2009-01-12 12:14 ` Balbir Singh
2009-01-15 6:19 ` KAMEZAWA Hiroyuki
2009-01-15 6:19 ` KAMEZAWA Hiroyuki
2009-01-08 9:32 ` [RFC][PATCH 3/4] memcg: fix OOM KILL under hierarchy KAMEZAWA Hiroyuki
2009-01-08 9:32 ` KAMEZAWA Hiroyuki
2009-01-13 8:33 ` Li Zefan [this message]
2009-01-13 8:33 ` Li Zefan
2009-01-13 9:25 ` KAMEZAWA Hiroyuki
2009-01-13 9:25 ` KAMEZAWA Hiroyuki
2009-01-08 9:35 ` [RFC][PATCH 4/4] cgroup-memcg fix frequent EBUSY at rmdir KAMEZAWA Hiroyuki
2009-01-08 9:35 ` KAMEZAWA Hiroyuki
2009-01-14 2:48 ` Paul Menage
2009-01-14 2:48 ` Paul Menage
2009-01-14 3:00 ` KAMEZAWA Hiroyuki
2009-01-14 3:00 ` KAMEZAWA Hiroyuki
2009-01-14 3:05 ` Paul Menage
2009-01-14 3:05 ` Paul Menage
2009-01-14 3:12 ` KAMEZAWA Hiroyuki
2009-01-14 3:12 ` KAMEZAWA Hiroyuki
2009-01-20 10:47 ` [RFC][PATCH 4/4] cgroup-memcg fix frequent EBUSY at rmdir v2 KAMEZAWA Hiroyuki
2009-01-20 10:47 ` KAMEZAWA Hiroyuki
2009-01-21 10:00 ` Paul Menage
2009-01-21 10:00 ` Paul Menage
2009-01-21 10:32 ` KAMEZAWA Hiroyuki
2009-01-21 10:32 ` KAMEZAWA Hiroyuki
2009-01-21 10:43 ` Paul Menage
2009-01-21 10:43 ` Paul Menage
2009-01-21 10:45 ` KAMEZAWA Hiroyuki
2009-01-21 10:45 ` 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=496C51C8.5040900@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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.