From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755173AbbK3WRI (ORCPT ); Mon, 30 Nov 2015 17:17:08 -0500 Received: from mail-pa0-f53.google.com ([209.85.220.53]:34030 "EHLO mail-pa0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755052AbbK3WRF (ORCPT ); Mon, 30 Nov 2015 17:17:05 -0500 Date: Mon, 30 Nov 2015 14:17:03 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Michal Hocko cc: Andrew Morton , Mel Gorman , Johannes Weiner , linux-mm@kvack.org, LKML Subject: Re: [PATCH 1/2] mm, oom: Give __GFP_NOFAIL allocations access to memory reserves In-Reply-To: <20151126093427.GA7953@dhcp22.suse.cz> Message-ID: References: <1448448054-804-1-git-send-email-mhocko@kernel.org> <1448448054-804-2-git-send-email-mhocko@kernel.org> <20151125111801.GD27283@dhcp22.suse.cz> <20151126093427.GA7953@dhcp22.suse.cz> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 26 Nov 2015, Michal Hocko wrote: > > > diff --git a/mm/page_alloc.c b/mm/page_alloc.c > > > index 8034909faad2..94b04c1e894a 100644 > > > --- a/mm/page_alloc.c > > > +++ b/mm/page_alloc.c > > > @@ -2766,8 +2766,13 @@ __alloc_pages_may_oom(gfp_t gfp_mask, unsigned int order, > > > goto out; > > > } > > > /* Exhausted what can be done so it's blamo time */ > > > - if (out_of_memory(&oc) || WARN_ON_ONCE(gfp_mask & __GFP_NOFAIL)) > > > + if (out_of_memory(&oc) || WARN_ON_ONCE(gfp_mask & __GFP_NOFAIL)) { > > > *did_some_progress = 1; > > > + > > > + if (gfp_mask & __GFP_NOFAIL) > > > + page = get_page_from_freelist(gfp_mask, order, > > > + ALLOC_NO_WATERMARKS, ac); > > > + } > > > out: > > > mutex_unlock(&oom_lock); > > > return page; > > > > Well, sure, that's one way to do it, but for cpuset users, wouldn't this > > lead to a depletion of the first system zone since you've dropped > > ALLOC_CPUSET and are doing ALLOC_NO_WATERMARKS in the same call? > > Are you suggesting to do? > if (gfp_mask & __GFP_NOFAIL) { > page = get_page_from_freelist(gfp_mask, order, > ALLOC_NO_WATERMARKS|ALLOC_CPUSET, ac); > /* > * fallback to ignore cpuset if our nodes are > * depleted > */ > if (!page) > get_page_from_freelist(gfp_mask, order, > ALLOC_NO_WATERMARKS, ac); > } > > I am not really sure this worth complication. I'm objecting to the ability of a process that is doing a __GFP_NOFAIL allocation, which has been disallowed access from allocating on certain mems through cpusets, to cause an oom condition on those disallowed nodes, yes.