If you set up cpu+memory cgroup properly, I think it works well. For well scheduled servers or some production devices, all applications and relationship of them can be designed properly and you can find the best cgroup set. For a some desktop environ like mine, which has 1-4G of memory, I think a user doesn't want to divide resources (limiting memory) for emergency because I want to use full resources of my poor host. Of course, I use memcg when I handle very big file or memory by an application when I can think of bad effects of that. And, with experiences in ML.... I've advised "please use memcg" when I see emails/questions about OOM....but there are still periodic OOM report to ML ;) Maybe usual users doesn't pay costs to avoid some emergency by themselves. (Some good daemon software should do that.) I feel the kernel itself should have the last resort to quit hard-to-recover status. Thanks, -Kame -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>