From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f69.google.com (mail-pl0-f69.google.com [209.85.160.69]) by kanga.kvack.org (Postfix) with ESMTP id 394AB6B0069 for ; Wed, 20 Dec 2017 20:41:06 -0500 (EST) Received: by mail-pl0-f69.google.com with SMTP id y36so10548418plh.10 for ; Wed, 20 Dec 2017 17:41:06 -0800 (PST) Received: from mga14.intel.com (mga14.intel.com. [192.55.52.115]) by mx.google.com with ESMTPS id o32si13792934pld.552.2017.12.20.17.41.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Dec 2017 17:41:05 -0800 (PST) Subject: Re: [PATCH v2 4/5] mm: use node_page_state_snapshot to avoid deviation References: <1513665566-4465-1-git-send-email-kemi.wang@intel.com> <1513665566-4465-5-git-send-email-kemi.wang@intel.com> <20171219124317.GP2787@dhcp22.suse.cz> <94187fd5-ad70-eba7-2724-0fe5bed750d6@intel.com> <20171220100650.GI4831@dhcp22.suse.cz> <1f3a6d05-2756-93fd-a380-df808c94ece8@intel.com> From: kemi Message-ID: <1f0d8933-60a3-e2e0-f7a3-36e98ade48bb@intel.com> Date: Thu, 21 Dec 2017 09:39:01 +0800 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: Christopher Lameter Cc: Michal Hocko , Greg Kroah-Hartman , Andrew Morton , Vlastimil Babka , Mel Gorman , Johannes Weiner , YASUAKI ISHIMATSU , Andrey Ryabinin , Nikolay Borisov , Pavel Tatashin , David Rientjes , Sebastian Andrzej Siewior , Dave , Andi Kleen , Tim Chen , Jesper Dangaard Brouer , Ying Huang , Aaron Lu , Aubrey Li , Linux MM , Linux Kernel On 2017a1'12ae??20ae?JPY 23:58, Christopher Lameter wrote: > On Wed, 20 Dec 2017, kemi wrote: > >>> You are making numastats special and I yet haven't heard any sounds >>> arguments for that. But that should be discussed in the respective >>> patch. >>> >> >> That is because we have much larger threshold size for NUMA counters, that means larger >> deviation. So, the number in local cpus may not be simply ignored. > > Some numbers showing the effect of these changes would be helpful. You can > probably create some in kernel synthetic tests to start with which would > allow you to see any significant effects of those changes. > > Then run the larger testsuites (f.e. those that Mel has published) and > benchmarks to figure out how behavior of real apps *may* change? > OK. I will do that when available. Let's just drop this patch in this series and consider this issue in another patch. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org