Re: [RFC PATCH] mm, oom: move GFP_NOFS check to out_of_memory

From: David Rientjes
Date: Tue Mar 29 2016 - 18:14:01 EST

On Tue, 29 Mar 2016, Michal Hocko wrote:

> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 86349586eacb..1c2b7a82f0c4 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -876,6 +876,10 @@ bool out_of_memory(struct oom_control *oc)
> return true;
> }
> + /* The OOM killer does not compensate for IO-less reclaim. */
> + if (!(oc->gfp_mask & __GFP_FS))
> + return true;
> +
> /*
> * Check if there were limitations on the allocation (only relevant for
> * NUMA) that may require different handling.

I don't object to this necessarily, but I think we need input from those
that have taken the time to implement their own oom notifier to see if
they agree. In the past, they would only be called if reclaim has
completely failed; now, they can be called in low memory situations when
reclaim has had very little chance to be successful. Getting an ack from
them would be helpful.

I also think we have discussed this before, but I think the oom notifier
handling should be in done in the page allocator proper, i.e. in
__alloc_pages_may_oom(). We can leave out_of_memory() for a clear defined
purpose: to kill a process when all reclaim has failed.