From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
pbadari@us.ibm.com, jblunck@suse.de, taka@valinux.co.jp,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
npiggin@suse.de
Subject: Re: [PATCH 0/2] memcg: fix oom handling
Date: Sat, 22 Nov 2008 10:16:25 +0800 [thread overview]
Message-ID: <49276B79.9060002@cn.fujitsu.com> (raw)
In-Reply-To: <20081121185829.e04c8116.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> Li Zefan reported
>
> (a) This goes dead lock:
> ==
> #echo 0 > (...)/01/memory.limit_in_bytes #set memcg's limit to 0,
> #echo $$ > (...)/01/memory.tasks #move task
> # do something...
> ==
>
> (b) seems to be dead lock
> ==
> #echo 40k > (...)/01/memory.limit_in_bytes #set memcg's limit to 0,
> #echo $$ > (...)/01/memory.tasks #move task
> # do something...
> ==
>
>
> I think (a) is BUG. (b) is just slow down.
> (you can see pgpgin/pgpgout count is increasing in (B).)
>
> This patch set is for handling (a). Li-san, could you check ?
Yes, it works for me now. :)
> This works well in my environment.(means OOM-Killer is called in proper way.)
>
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>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
pbadari@us.ibm.com, jblunck@suse.de, taka@valinux.co.jp,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
npiggin@suse.de
Subject: Re: [PATCH 0/2] memcg: fix oom handling
Date: Sat, 22 Nov 2008 10:16:25 +0800 [thread overview]
Message-ID: <49276B79.9060002@cn.fujitsu.com> (raw)
In-Reply-To: <20081121185829.e04c8116.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> Li Zefan reported
>
> (a) This goes dead lock:
> ==
> #echo 0 > (...)/01/memory.limit_in_bytes #set memcg's limit to 0,
> #echo $$ > (...)/01/memory.tasks #move task
> # do something...
> ==
>
> (b) seems to be dead lock
> ==
> #echo 40k > (...)/01/memory.limit_in_bytes #set memcg's limit to 0,
> #echo $$ > (...)/01/memory.tasks #move task
> # do something...
> ==
>
>
> I think (a) is BUG. (b) is just slow down.
> (you can see pgpgin/pgpgout count is increasing in (B).)
>
> This patch set is for handling (a). Li-san, could you check ?
Yes, it works for me now. :)
> This works well in my environment.(means OOM-Killer is called in proper way.)
>
--
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:[~2008-11-22 2:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 10:12 [PATCH 0/9] memcg updates (14/Nov/2008) KAMEZAWA Hiroyuki
2008-11-14 10:12 ` KAMEZAWA Hiroyuki
2008-11-14 10:14 ` [PATCH 1/9] memcg: memory hotpluf fix for notifier callback KAMEZAWA Hiroyuki
2008-11-14 10:14 ` KAMEZAWA Hiroyuki
2008-11-14 10:15 ` [PATCH 2/9] memcg : reduce size of mem_cgroup by using nr_cpu_ids KAMEZAWA Hiroyuki
2008-11-14 10:15 ` KAMEZAWA Hiroyuki
2008-11-14 10:16 ` [PATCH 3/9] memcg: new force_empty to free pages under group KAMEZAWA Hiroyuki
2008-11-14 10:16 ` KAMEZAWA Hiroyuki
2008-11-14 10:17 ` [PATCH 4/9] memcg: handle swap caches KAMEZAWA Hiroyuki
2008-11-14 10:17 ` KAMEZAWA Hiroyuki
2008-11-14 10:18 ` [PATCH 5/9] memcg : mem+swap controller Kconfig KAMEZAWA Hiroyuki
2008-11-14 10:18 ` KAMEZAWA Hiroyuki
2008-11-14 10:18 ` [PATCH 6/9] memcg : swap cgroup for remembering usage KAMEZAWA Hiroyuki
2008-11-14 10:18 ` KAMEZAWA Hiroyuki
2008-11-14 10:19 ` [PATCH 7/9] memcg : mem+swap controlelr core KAMEZAWA Hiroyuki
2008-11-14 10:19 ` KAMEZAWA Hiroyuki
2008-11-21 2:40 ` Li Zefan
2008-11-21 2:40 ` Li Zefan
2008-11-21 2:44 ` KAMEZAWA Hiroyuki
2008-11-21 2:44 ` KAMEZAWA Hiroyuki
2008-11-21 9:58 ` [PATCH 0/2] memcg: fix oom handling KAMEZAWA Hiroyuki
2008-11-21 9:58 ` KAMEZAWA Hiroyuki
2008-11-21 10:01 ` [PATCH 1/2] memcg: avoid unnecessary system-wide-oom-killer KAMEZAWA Hiroyuki
2008-11-21 10:01 ` KAMEZAWA Hiroyuki
2008-11-21 10:03 ` [PATCH 2/2] memcg: fix reclaim result checks KAMEZAWA Hiroyuki
2008-11-21 10:03 ` KAMEZAWA Hiroyuki
2008-11-22 2:16 ` Li Zefan [this message]
2008-11-22 2:16 ` [PATCH 0/2] memcg: fix oom handling Li Zefan
2008-11-14 10:20 ` [PATCH 8/9] memcg : synchronized LRU KAMEZAWA Hiroyuki
2008-11-14 10:20 ` KAMEZAWA Hiroyuki
2008-11-14 10:21 ` [PATCH 9/9] memcg : add mem_cgroup_disabled() KAMEZAWA Hiroyuki
2008-11-14 10:21 ` KAMEZAWA Hiroyuki
2008-11-14 11:33 ` [PATCH 0/9] memcg updates (14/Nov/2008) Balbir Singh
2008-11-14 11:33 ` Balbir Singh
2008-11-15 3:00 ` KAMEZAWA Hiroyuki
2008-11-15 7:25 ` Balbir Singh
2008-11-15 9:16 ` KAMEZAWA Hiroyuki
2008-11-15 9:19 ` Balbir Singh
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=49276B79.9060002@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=jblunck@suse.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=npiggin@suse.de \
--cc=pbadari@us.ibm.com \
--cc=taka@valinux.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.