Messages in this thread | | | Date | Wed, 2 Dec 2015 16:01:18 -0800 (PST) | From | David Rientjes <> | Subject | Re: [PATCH v2] mm, oom: Give __GFP_NOFAIL allocations access to memory reserves |
| |
On Wed, 2 Dec 2015, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.com> > > __GFP_NOFAIL is a big hammer used to ensure that the allocation > request can never fail. This is a strong requirement and as such > it also deserves a special treatment when the system is OOM. The > primary problem here is that the allocation request might have > come with some locks held and the oom victim might be blocked > on the same locks. This is basically an OOM deadlock situation. > > This patch tries to reduce the risk of such a deadlocks by giving > __GFP_NOFAIL allocations a special treatment and let them dive into > memory reserves after oom killer invocation. This should help them > to make a progress and release resources they are holding. The OOM > victim should compensate for the reserves consumption. > > Suggested-by: Andrea Arcangeli <aarcange@redhat.com> > Signed-off-by: Michal Hocko <mhocko@suse.com>
Acked-by: David Rientjes <rientjes@google.com>
| |