Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp338215yba; Thu, 18 Apr 2019 02:03:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqwS+Db+sL4wRWazY5Rf7R5+s/cDDfxd07Q5p/WJcF/oMwJZrr9lRZeiRZ2uPrOkeejK872F X-Received: by 2002:a63:1247:: with SMTP id 7mr86645316pgs.352.1555578238183; Thu, 18 Apr 2019 02:03:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555578238; cv=none; d=google.com; s=arc-20160816; b=By8LT8S5wVXzGIG5/Pi0hPlNwWuPbSR1eLXzdJpGGX3O8rjg0VEUsaicbkOMjamzCA 8HP7qATR69FAl7s4uQXyyj3ZF8gGiZqngmPzKagRKdq5NGrk0tWNbA6cb60hFYFWCyw1 PZhH8/8GdVe9ZM92qC7oJrH3HulXvHQJ/6RdguID0eZ4ZGiJpOsmJunrjd7lV7q+P+eq PxjlTfllG93YJzKHZ+IiCmLXbpatdE4iGv1HbffD8DA/cbW5KfFolmUEdVIwoc65JO35 SBhhKqOQdUla0dqEy83hqC0tah69PTT9ye3f1k0rv55bfhie7JAG5So4B9XdMkTOHEWX mgjg== 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=DoQyDe4iN4rSDSn59KCg88licv4gudixO5kqMTZt/aM=; b=vVyXOzaXYGLEebmEFEkCfeSnuy/S8RD8wJANOePzT7E0XB4nb+Imqoc5VfgwxuqO89 QxuJE8QZGEx2WmuWuJiFBB2NwZQCI7DolhT9HilceXTkGi2iSi8awpZIdPHrfLGthf+n 2k7mHpX4gT1DRO/SuQM7CG5AIANBOSEy9ACOu/m9ZH/9FUs9p9Z6V4id+G+LXnheBl5r VYNrDIkqtm4+6rHPFJAhB+xEQJ1YVc/SClPVB5eThNzhKvPTEqTUVCjavsDUgjjjF/4N FFV+5OacCrHgV0Ml54S6woG07TC0m8fK4CpwF5sDZOq2pspXX6nRvRlGCv70LM5MghRT oVoQ== 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 c24si1614179plo.220.2019.04.18.02.03.43; Thu, 18 Apr 2019 02:03:58 -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 S2388363AbfDRJCb (ORCPT + 99 others); Thu, 18 Apr 2019 05:02:31 -0400 Received: from mx2.suse.de ([195.135.220.15]:46622 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2388036AbfDRJCa (ORCPT ); Thu, 18 Apr 2019 05:02:30 -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 8FE47AEBB; Thu, 18 Apr 2019 09:02:28 +0000 (UTC) Date: Thu, 18 Apr 2019 11:02:27 +0200 From: Michal Hocko To: Yang Shi Cc: mgorman@techsingularity.net, riel@surriel.com, hannes@cmpxchg.org, akpm@linux-foundation.org, dave.hansen@intel.com, keith.busch@intel.com, dan.j.williams@intel.com, fengguang.wu@intel.com, fan.du@intel.com, ying.huang@intel.com, ziy@nvidia.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [v2 RFC PATCH 0/9] Another Approach to Use PMEM as NUMA Node Message-ID: <20190418090227.GG6567@dhcp22.suse.cz> References: <1554955019-29472-1-git-send-email-yang.shi@linux.alibaba.com> <20190412084702.GD13373@dhcp22.suse.cz> <20190416074714.GD11561@dhcp22.suse.cz> <876768ad-a63a-99c3-59de-458403f008c4@linux.alibaba.com> 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 17-04-19 13:43:44, Yang Shi wrote: [...] > And, I'm wondering whether this optimization is also suitable to general > NUMA balancing or not. If there are convincing numbers then this should be a preferable way to deal with it. Please note that the number of promotions is not the only metric to watch. The overal performance/access latency would be another one. -- Michal Hocko SUSE Labs