Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp9902925imu; Wed, 5 Dec 2018 12:17:02 -0800 (PST) X-Google-Smtp-Source: AFSGD/VBpnVpuH+6NBYdQrNv2PvgWo75LN5xqoJQbSugqNXS5AZiiwVIRIAz2MyEjrMYFjkbalXv X-Received: by 2002:a63:1258:: with SMTP id 24mr21435881pgs.114.1544041022214; Wed, 05 Dec 2018 12:17:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544041022; cv=none; d=google.com; s=arc-20160816; b=XAJoBYFpRXhpTqED7AUgXKhp06QgGZrwpj6sagQ83OL0y9/QFPoJsxUk45Isb2KvOE 2ihjZmofDhrI3uVSWO8gNTycpg9MztVmUMnAJ7E6ihkLNdZJcqtzLYEwlvu19n4UWmmm Lifpr+wyay2KgULsF5PjOjLTI3X1uAcluyJdmLnnz+K63CN1EeRngeoWDk1k3xAmOtt6 +saQ6puPDYl+jNKWDtvwx/4HjDhwjaSyUV4/HrG9diRjN6x6c+kgMgBsykQieJlRyDjA f7nZnRnwKuSxkUWjp3DSNOkn+sx6TK+5g47fBHF/TaGNGfNq6TU5dLTV8RWGWiiJeB31 wHTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Rs0zRacc+JmCQLHitgRWUT3YhDlJMG99Z7czXEJ45Kk=; b=Tdd5ZoUbuq9wKE1Nx3U+J/ITzFkYG6Ji2F3TSPi11762uu//XwURzjAS3O521LHxl1 CSGsgmwMTcHTBVppKzx5MtRwbmrTlGOOR4LU1fACzQKRJJIKLNENkWub+9wqHWF/kKC7 5wNxwm9XcP8xLl4jzikAu/JHBugcRPwIMr2YR28SKZpZWsahyRDkD7CdhndDTMFgT+WN zgDm1Vn0YmRMRn2op1klFavQH706H6reCCRLTJR4U5n5hi9Yd6gPgf9HK10yZQKav2eu aeyKR0pWBx+xkeaf9sEu/xl+Tfe+y3sQWn4L1rzV7g6sTr+ScckfyVRKoHo80LxZB6i5 nHyw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s191si23657463pfs.53.2018.12.05.12.16.46; Wed, 05 Dec 2018 12:17:02 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728490AbeLEUPe (ORCPT + 99 others); Wed, 5 Dec 2018 15:15:34 -0500 Received: from mx2.suse.de ([195.135.220.15]:52096 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727257AbeLEUPe (ORCPT ); Wed, 5 Dec 2018 15:15:34 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C8923ACAB; Wed, 5 Dec 2018 20:15:31 +0000 (UTC) Date: Wed, 5 Dec 2018 21:15:28 +0100 From: Michal Hocko To: David Rientjes Cc: Linus Torvalds , Andrea Arcangeli , ying.huang@intel.com, s.priebe@profihost.ag, mgorman@techsingularity.net, Linux List Kernel Mailing , alex.williamson@redhat.com, lkp@01.org, kirill@shutemov.name, Andrew Morton , zi.yan@cs.rutgers.edu, Vlastimil Babka Subject: Re: [patch 1/2 for-4.20] mm, thp: restore node-local hugepage allocations Message-ID: <20181205201528.GW1286@dhcp22.suse.cz> References: <20181204073535.GV31738@dhcp22.suse.cz> <20181205073434.GT1286@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 05-12-18 11:24:53, David Rientjes wrote: > On Wed, 5 Dec 2018, Michal Hocko wrote: > > > > > At minimum do not remove the cleanup part which consolidates the gfp > > > > hadnling to a single place. There is no real reason to have the > > > > __GFP_THISNODE ugliness outside of alloc_hugepage_direct_gfpmask. > > > > > > > > > > The __GFP_THISNODE usage is still confined to > > > alloc_hugepage_direct_gfpmask() for the thp fault path, we no longer set > > > it in alloc_pages_vma() as done before the cleanup. > > > > Why should be new_page any different? > > > > To match alloc_new_node_page() which does it correctly and does not change > the behavior of mbind() that the cleanup did, which used > alloc_hugepage_vma() to get the __GFP_THISNODE behavior. If there is a > reason mbind() is somehow different wrt allocating hugepages locally, I > think that should be a separate patch, but the goal of this patch is to > revert all the behavioral change that caused hugepages to be allocated > remotely. If the __GFP_THISNODE should be really used then it should be applied to all other types of pages. Not only THP. And as such done in a separate patch. Not a part of the revert. The cleanup was meant to unify THP allocations and that is why I object to reverting it as a part of this work. -- Michal Hocko SUSE Labs