Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1771314yba; Thu, 25 Apr 2019 05:35:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqxnbwMvSmSGiFVFsxvs+NysGtJE+alfcqN43IPMOFKrNeKjoAZlc+4h8TJooDw0Sdv+gdvg X-Received: by 2002:aa7:82d6:: with SMTP id f22mr30947451pfn.190.1556195710462; Thu, 25 Apr 2019 05:35:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556195710; cv=none; d=google.com; s=arc-20160816; b=jY0V5IFzLzkZ/MHsNQzXzv1c8k1e3IXqxiusN/14+MFcohfSIQBAaC6zjdHhxMAKsv JlLERt5CWyp5E07F2g2HlQlB3FFEtKhNvigt6+XblqxPVF1iEfGbg1Q4ZXPO91Dmf/J7 qRiu1y3fAiNKlfB2m/QRQhu6yG7GkrPNptmyowqR3gB1qJBQ19sRkhEJxJbtDi87Uuy8 a9o9VlJEurx+E+ZzCkchSTZrQYm7XEfAia8mtkAt12p5tDBqf+ySCyX5LyIJoL64hGcb QezHGs/5FtBoau/JM1/RJWwPPUw61ahfsh15XpexO4TANtDmuEM+CBAcoZXR7YwYrf53 FpVg== 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=6bCTRhaJZcHleBm+PC1JlrZO4wAxSCu2khUzsJ1UBUs=; b=SyAA2/L9+Js84RWN4Sh2W24WDei7iMkGGwuVgjI1d3xrq7XmiD4IGTA9/u+IkI+Ycm 5D7o110rNZm7iNSIMZJCScCL5Ofp9PxQBNv+2xjSJTCaugvfNL1k3Si06Bjt8wkKFg+z dSPwls1N6YYwO5p/STDm8vBEtSQezAZq1w2YCgJSNNeXjCu8dYMSBuGEDd4swrtpVCk0 qLOKwy/8KYpMMvtNoCj8XoXUyVP0Byunn378thsJ0ovj71zJ/OzjllTEPFUMEYKw9QZW ZLDReCDtzny5qqdmi4B875G6VHzPhZAAct1n6wmBOR0WE/M/GGTSHxCCLDG0lQtmscEm 16gQ== 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 h3si13474636pgb.250.2019.04.25.05.34.53; Thu, 25 Apr 2019 05:35:10 -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 S1726546AbfDYInF (ORCPT + 99 others); Thu, 25 Apr 2019 04:43:05 -0400 Received: from mx2.suse.de ([195.135.220.15]:48796 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725965AbfDYInE (ORCPT ); Thu, 25 Apr 2019 04:43:04 -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 A9156AD18; Thu, 25 Apr 2019 08:43:03 +0000 (UTC) Date: Thu, 25 Apr 2019 10:43:02 +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: <20190425084302.GQ12751@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> <20190425080936.GP12751@dhcp22.suse.cz> <5A90DA2E42F8AE43BC4A093BF067884825785FA5@SHSMSX104.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A90DA2E42F8AE43BC4A093BF067884825785FA5@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 08:20:28, Du, Fan wrote: > > > >-----Original Message----- > >From: owner-linux-mm@kvack.org [mailto:owner-linux-mm@kvack.org] On > >Behalf Of Michal Hocko > >Sent: Thursday, April 25, 2019 4:10 PM > >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 > > > >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 > > Sorry, I mean page cache case here. > Numa balancing works for pages mapped in pagetable style. I would still expect that a remote PMEM node access latency is smaller/comparable to the real storage so a promoting part is not that important for the unmapped pagecache. Maybe I am wrong here but that really begs for some experiments before we start adding special casing. -- Michal Hocko SUSE Labs