Messages in this thread | | | Date | Fri, 10 Jan 2014 09:30:25 +0100 | From | Michal Hocko <> | Subject | Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves |
| |
On Thu 09-01-14 16:01:15, David Rientjes wrote: > On Thu, 9 Jan 2014, Andrew Morton wrote: > > > > 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
| |