Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked
From: azurIt <hidden>
Date: 2012-11-30 02:29:23
Also in:
cgroups, lkml
Possibly related (same subject, not in this thread)
- 2013-02-08 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Michal Hocko <hidden>
- 2013-02-08 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Michal Hocko <hidden>
- 2013-02-08 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Greg Thelen <hidden>
- 2013-02-05 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Michal Hocko <hidden>
- 2013-02-05 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Greg Thelen <hidden>
Here we go with the patch for 3.2.34. Could you test with this one, please?
Michal, unfortunately i had to boot to another kernel because the one with this patch keeps killing my MySQL server :( it was, probably, doing it on OOM in any cgroup - looks like OOM was not choosing processes only from cgroup which is out of memory. Here is the log from syslog: http://www.watchdog.sk/lkml/oom_mysqld Maybe i should mention that MySQL server has it's own cgroup (called 'mysql') but with no limits to any resources. azurIt -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>