Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp1188869ima; Wed, 24 Oct 2018 16:18:38 -0700 (PDT) X-Google-Smtp-Source: AJdET5d7BvZ/xJ7NsLq6EpF5/3A8UP69JufwJ0/W4VXwDfer+CkR/rpnK8bHM7CT/1sDHJhCVLe2 X-Received: by 2002:a17:902:5602:: with SMTP id h2-v6mr4244264pli.220.1540423118317; Wed, 24 Oct 2018 16:18:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540423118; cv=none; d=google.com; s=arc-20160816; b=EBW/zSPD+nkdXVGmv105No7U5ItpDe1kJeaYiN7AvHOApJyRsiAe2Mze4Io/1YaVzc o59QqILEeYb3HHIDtMxHLAWPvrWI/yGABBSReQT148UbQpuhijXHcr61mMV0LA/D8k7M wT3BPmGhwx+CiJpV3OCUYFs1AUgp4D0na9eq9Gh4JJNZAjqVxfSM9daSaTXXStQWayA7 mic5VI4Qwhlj14t1Pf8mZnUmXuHuTHZJGIXePAiSCy2ZgjwJNlVkplXdAdiqyf+qYPY4 RhT9rrsW/iTJJiIRVqSLzorDgY5M4FWqdFtI6+iUD+C+gTHmaROb+x2hBKfg2tINK9cI UwIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=hvlsIsnntsJZrkRui/eMkl4y6h/5RaLNRKE7zJMYW+Q=; b=bYUcz7Tuc4FZDukY3RNpGpZRmFppuSRdvhzByZUd5OdCs4jwWCMthJV09ZTqDNojeX j7oFYHgBWYxGVsLfMGVDswziZfzIJiidj4BnaTzCbT++kJ47pyCPW1OG9RcxhfGU66rw ImeLIpmVAjHmbZ0M8lvYTT9OnxrpPllF+hfy7FTITl7i663BkfTSuWozpxAwXVCye+tL Ty/PGnF/4IkR6fuDc54XSAj0sh8DXqwNi4kUnvAlViwTjiBc2w8E07lpN0PwT7Zl/VWh bflYG42U+KJcyf+csKStGU53v/WZIXExULB4rYZEL2a2LmhgkRYsTsysfpGQPXZFI3Un t3+A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w5-v6si6149834pgw.184.2018.10.24.16.18.19; Wed, 24 Oct 2018 16:18:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726716AbeJYHr7 (ORCPT + 99 others); Thu, 25 Oct 2018 03:47:59 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:49188 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726236AbeJYHr6 (ORCPT ); Thu, 25 Oct 2018 03:47:58 -0400 Received: from akpm3.svl.corp.google.com (unknown [104.133.8.65]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 97C6E1837; Wed, 24 Oct 2018 23:17:55 +0000 (UTC) Date: Wed, 24 Oct 2018 16:17:54 -0700 From: Andrew Morton To: Vlastimil Babka Cc: Michal Hocko , "Kirill A. Shutemov" , Mel Gorman , David Rientjes , Andrea Argangeli , Zi Yan , Stefan Priebe - Profihost AG , linux-mm@kvack.org, LKML Subject: Re: [PATCH 2/2] mm, thp: consolidate THP gfp handling into alloc_hugepage_direct_gfpmask Message-Id: <20181024161754.0d174e7c22113f4f8aad1940@linux-foundation.org> In-Reply-To: <583b20e5-4925-e175-1533-5c2d2bab9192@suse.cz> References: <20180925120326.24392-1-mhocko@kernel.org> <20180925120326.24392-3-mhocko@kernel.org> <20180926133039.y7o5x4nafovxzh2s@kshutemo-mobl1> <20180926141708.GX6278@dhcp22.suse.cz> <20180926142227.GZ6278@dhcp22.suse.cz> <20181018191147.33e8d5e1ebd785c06aab7b30@linux-foundation.org> <20181019080657.GJ18839@dhcp22.suse.cz> <583b20e5-4925-e175-1533-5c2d2bab9192@suse.cz> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 22 Oct 2018 15:27:54 +0200 Vlastimil Babka wrote: > > : Moreover the oriinal code allowed to trigger > > : WARN_ON_ONCE(policy->mode == MPOL_BIND && (gfp & __GFP_THISNODE)); > > : in policy_node if the requested node (e.g. cpu local one) was outside of > > : the mbind nodemask. This is not possible now. We haven't heard about any > > : such warning yet so it is unlikely that it happens but still a signal of > > : a wrong code layering. > > Ah, as I said in the other mail, I think it's inaccurate, the warning > was not possible to hit. > > There's also a slight difference wrt MPOL_BIND. The previous code would > avoid using __GFP_THISNODE if the local node was outside of > policy_nodemask(). After your patch __GFP_THISNODE is avoided for all > MPOL_BIND policies. So there's a difference that if local node is > actually allowed by the bind policy's nodemask, previously > __GFP_THISNODE would be added, but now it won't be. I don't think it > matters that much though, but maybe the changelog could say that > (instead of the inaccurate note about warning). Note the other policy > where nodemask is relevant is MPOL_INTERLEAVE, and that's unchanged by > this patch. So the above could go into the changelog, yes? > When that's addressed, you can add What is it that you'd like to see addressed? Purely changelog updates? > Acked-by: Vlastimil Babka Thanks.