From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: linux-mm <linux-mm@kvack.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: [RFC][PATCH 6/8] memcg: avoid oom during recharge at task move
Date: Tue, 13 Oct 2009 13:56:11 +0900 [thread overview]
Message-ID: <20091013135611.9eb51eb3.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20091013134903.66c9682a.nishimura@mxp.nes.nec.co.jp>
This recharge-at-task-move feature has extra charges(pre-charges) on "to"
mem_cgroup during recharging. This means unnecessary oom can happen.
This patch tries to avoid such oom.
Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
---
mm/memcontrol.c | 27 +++++++++++++++++++++++++++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 85fee0c..88b3fc2 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -206,6 +206,7 @@ struct recharge_struct {
struct mem_cgroup *from;
struct mem_cgroup *to;
struct task_struct *target; /* the target task being moved */
+ struct task_struct *working; /* a task moving the target task */
unsigned long precharge;
};
static struct recharge_struct recharge;
@@ -1526,6 +1527,30 @@ static int __mem_cgroup_try_charge(struct mm_struct *mm,
if (mem_cgroup_check_under_limit(mem_over_limit))
continue;
+ /* try to avoid oom while someone is recharging */
+ if (recharge.working && current != recharge.working) {
+ struct mem_cgroup *dest;
+ bool do_continue = false;
+ /*
+ * There is a small race that "dest" can be freed by
+ * rmdir, so we use css_tryget().
+ */
+ rcu_read_lock();
+ dest = recharge.to;
+ if (dest && css_tryget(&dest->css)) {
+ if (dest->use_hierarchy)
+ do_continue = css_is_ancestor(
+ &dest->css,
+ &mem_over_limit->css);
+ else
+ do_continue = (dest == mem_over_limit);
+ css_put(&dest->css);
+ }
+ rcu_read_unlock();
+ if (do_continue)
+ continue;
+ }
+
if (!nr_retries--) {
if (oom) {
mutex_lock(&memcg_tasklist);
@@ -3580,6 +3605,7 @@ static void mem_cgroup_clear_recharge(void)
recharge.from = NULL;
recharge.to = NULL;
recharge.target = NULL;
+ recharge.working = NULL;
}
static int mem_cgroup_can_recharge(struct mem_cgroup *mem,
@@ -3594,6 +3620,7 @@ static int mem_cgroup_can_recharge(struct mem_cgroup *mem,
recharge.from = from;
recharge.to = mem;
recharge.target = p;
+ recharge.working = current;
recharge.precharge = 0;
ret = mem_cgroup_recharge_prepare();
--
1.5.6.1
--
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-10-13 5:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 4:49 [RFC][PATCH 0/8] memcg: recharge at task move (Oct13) Daisuke Nishimura
2009-10-13 4:50 ` [RFC][PATCH 1/8] cgroup: introduce cancel_attach() Daisuke Nishimura
2009-10-15 7:37 ` Paul Menage
2009-10-15 8:50 ` Paul Menage
2009-10-15 11:08 ` Daisuke Nishimura
2009-10-13 4:51 ` [RFC][PATCH 2/8] memcg: cleanup mem_cgroup_move_parent() Daisuke Nishimura
2009-10-13 4:52 ` [RFC][PATCH 3/8] memcg: move memcg_tasklist mutex Daisuke Nishimura
2009-10-13 4:53 ` [RFC][PATCH 4/8] memcg: add interface to recharge at task move Daisuke Nishimura
2009-10-13 4:55 ` [RFC][PATCH 5/8] memcg: recharge charges of mapped page Daisuke Nishimura
2009-10-13 4:56 ` Daisuke Nishimura [this message]
2009-10-13 4:57 ` [RFC][PATCH 7/8] memcg: recharge charges of anonymous swap Daisuke Nishimura
2009-10-13 4:58 ` [RFC][PATCH 8/8] memcg: recharge charges of shmem swap Daisuke Nishimura
2009-10-14 7:03 ` [RFC][PATCH 0/8] memcg: recharge at task move (Oct13) KAMEZAWA Hiroyuki
2009-10-15 0:27 ` Daisuke Nishimura
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=20091013135611.9eb51eb3.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.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