[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <49276B79.9060002@cn.fujitsu.com>
Date: Sat, 22 Nov 2008 10:16:25 +0800
From: Li Zefan <lizf@...fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
CC: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com>,
"nishimura@....nes.nec.co.jp" <nishimura@....nes.nec.co.jp>,
pbadari@...ibm.com, jblunck@...e.de, taka@...inux.co.jp,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
npiggin@...e.de
Subject: Re: [PATCH 0/2] memcg: fix oom handling
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists