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 <mhocko@xxxxxxx> wrote: > On Tue 23-10-12 11:35:52, Qiang Gao wrote: >> 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: >> cglimit -M 700M ./tt >> then after global-oom,the process hangs.. > >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
