this is just an example to show how to reproduce. actually,the first time I saw
this situation was on a machine with 288G RAM with many tasks running and
we limit 30G for each.  but finanlly, no one exceeds this limit the the system
oom.


On Tue, Oct 23, 2012 at 4:35 PM, Michal Hocko [off-list ref] wrote:

On Tue 23-10-12 11:35:52, Qiang Gao wrote:

quoted

I'm sure this is a global-oom,not cgroup-oom. [the dmesg output in the end]

Yes this is the global oom killer because:

quoted

cglimit -M 700M ./tt
then after global-oom,the process hangs..

quoted

179184 pages RAM

So you have ~700M of RAM so the memcg limit is basically pointless as it
cannot be reached...
--
Michal Hocko
SUSE Labs