Hi, It seems that when a process in some memcg tries to allocate more than memcg.limit_in_bytes, oom happens instead of swaping out in mmotm-2014-07-09-17-08 (memcg.memsw.limit_in_bytes is large enough). It does work in v3.16-rc3, so I think latest patches changed something. I'm not familiar with memcg internally, so no idea about what caused it. Could you see the problem? Thanks, Naoya Horiguchi -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
