Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1564232yba; Thu, 25 Apr 2019 01:48:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqxrnceW7j61kOINQcnWUZUy4ve693nWnRGoT+TJRu938hfLLWfwNMhOQRLK8VnrnZ843oG/ X-Received: by 2002:a17:902:1024:: with SMTP id b33mr36877599pla.46.1556182122895; Thu, 25 Apr 2019 01:48:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556182122; cv=none; d=google.com; s=arc-20160816; b=dleBsOMlBL3fWv4PjFhJyBmOZ6LRmXgbIu7dXmTYuvcXUdrxVxmzIcjGDyxmTmYDJR kvnePDR3jQYayxIZe/0bxDi7vUqJmY2bC/zQ8LidxhrIFxjikt/gGlnRLd3VX5tXklBc ZusN8HWzMcqvPxi1lADjpiAQZQ6zMH1oHu/j01QdtXaJXJo8WDn0ENUUemOpidbDigDn EHgQ1oXbHB0j+olyAgGRt8SfHf/YJnI2JInRR45C9HqGbiRF1u8JoDTsXAWAM9Ir0gvb qPqcZjbQm/YH7qhoLk3FAcbWAh4Wxpk85T5nV2aHmkbHhquSBC6fbRAvLCPJ/f/wsH6c xObw== 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=7gkg/7Xeis9rc+EVTWp9bsr+pgBSXPMB56OaXhmvYhM=; b=DACGTDkVbGIomZDWuhww1w1bB/wa6HHqnjTIdsG/zWeQwDbvfYvx40lu5Mdk0X0Hg5 CgN7k6wb5P401y/QiIN9dO++GPAHzHFQfzfeiOB61cbJPcM12+BEZd5yb8aYk7IMd2K7 dsa274kZ1F5nMSo5XE0Bb1rvKtLlFE/mlHlkYAhwxSonJ/v/DocYgy7KHt+wOUBSSF8E hRG4Cge8xxiHJm+UZzOJ5pB8ZqMdvmK4hfPxeigfpPNVUV1DiNR2fTHyGnBL9TLqiCAW /7W81gMLIyoni5CgEe4ESoXMFBH63Eu3KCBEbvIc0F/rkzk80+IVOVtWJkxA2nHsOLof 4hGQ== 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 h3si12937700pgb.250.2019.04.25.01.48.27; Thu, 25 Apr 2019 01:48:42 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728815AbfDYIJj (ORCPT + 99 others); Thu, 25 Apr 2019 04:09:39 -0400 Received: from mx2.suse.de ([195.135.220.15]:42954 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725980AbfDYIJi (ORCPT ); Thu, 25 Apr 2019 04:09:38 -0400 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 8E5FCAF58; Thu, 25 Apr 2019 08:09:37 +0000 (UTC) Date: Thu, 25 Apr 2019 10:09:36 +0200 From: Michal Hocko To: "Du, Fan" Cc: "akpm@linux-foundation.org" , "Wu, Fengguang" , "Williams, Dan J" , "Hansen, Dave" , "xishi.qiuxishi@alibaba-inc.com" , "Huang, Ying" , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list Message-ID: <20190425080936.GP12751@dhcp22.suse.cz> References: <1556155295-77723-1-git-send-email-fan.du@intel.com> <1556155295-77723-6-git-send-email-fan.du@intel.com> <20190425063807.GK12751@dhcp22.suse.cz> <5A90DA2E42F8AE43BC4A093BF067884825785F04@SHSMSX104.ccr.corp.intel.com> <20190425074841.GN12751@dhcp22.suse.cz> <5A90DA2E42F8AE43BC4A093BF067884825785F50@SHSMSX104.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A90DA2E42F8AE43BC4A093BF067884825785F50@SHSMSX104.ccr.corp.intel.com> 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 Thu 25-04-19 07:55:58, Du, Fan wrote: > >> PMEM is good for frequently read accessed page, e.g. page cache(implicit > >> page > >> request), or user space data base (explicit page request) > >> For now this patch create GFP_SAME_NODE_TYPE for such cases, additional > >> Implementation will be followed up. > > > >Then simply configure that NUMA node as movable and you get these > >allocations for any movable allocation. I am not really convinced a new > >gfp flag is really justified. > > Case 1: frequently write and/or read accessed page deserved to DRAM NUMA balancing > Case 2: frequently read accessed page deserved to PMEM memory reclaim to move those pages to a more distant node (e.g. a PMEM). Btw. none of the above is a static thing you would easily know at the allocation time. Please spare some time reading surrounding discussions - e.g. http://lkml.kernel.org/r/1554955019-29472-1-git-send-email-yang.shi@linux.alibaba.com -- Michal Hocko SUSE Labs