Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves
From: Michal Hocko <hidden>
Date: 2014-01-10 08:30:30
Also in:
linux-mm, lkml
From: Michal Hocko <hidden>
Date: 2014-01-10 08:30:30
Also in:
linux-mm, lkml
On Thu 09-01-14 16:01:15, David Rientjes wrote:
On Thu, 9 Jan 2014, Andrew Morton wrote:quoted
quoted
I'm not sure why this was dropped since it's vitally needed for any sane userspace oom handler to be effective.It was dropped because the other memcg developers disagreed with it.It was acked-by Michal.
I have already explained why I have acked it. I will not repeat it here again. I have also proposed an alternative solution (https://lkml.org/lkml/2013/12/12/174) which IMO is more viable because it handles both user/kernel memcg OOM consistently. This patch still has to be discussed because of other Johannes concerns. I plan to repost it in a near future. -- Michal Hocko SUSE Labs -- 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>