Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754904AbdLTKXp (ORCPT ); Wed, 20 Dec 2017 05:23:45 -0500 Received: from mga05.intel.com ([192.55.52.43]:43770 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754363AbdLTKXm (ORCPT ); Wed, 20 Dec 2017 05:23:42 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,431,1508828400"; d="scan'208";a="14182506" Subject: Re: [PATCH v2 3/5] mm: enlarge NUMA counters threshold size To: Michal Hocko Cc: Greg Kroah-Hartman , Andrew Morton , Vlastimil Babka , Mel Gorman , Johannes Weiner , Christopher Lameter , 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 References: <1513665566-4465-1-git-send-email-kemi.wang@intel.com> <1513665566-4465-4-git-send-email-kemi.wang@intel.com> <20171219124045.GO2787@dhcp22.suse.cz> <439918f7-e8a3-c007-496c-99535cbc4582@intel.com> <20171220101229.GJ4831@dhcp22.suse.cz> From: kemi Message-ID: <3a1f6441-30d9-6f45-af4b-efd53b01ee95@intel.com> Date: Wed, 20 Dec 2017 18:21:40 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171220101229.GJ4831@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1391 Lines: 34 On 2017年12月20日 18:12, Michal Hocko wrote: > On Wed 20-12-17 13:52:14, kemi wrote: >> >> >> On 2017年12月19日 20:40, Michal Hocko wrote: >>> On Tue 19-12-17 14:39:24, Kemi Wang wrote: >>>> We have seen significant overhead in cache bouncing caused by NUMA counters >>>> update in multi-threaded page allocation. See 'commit 1d90ca897cb0 ("mm: >>>> update NUMA counter threshold size")' for more details. >>>> >>>> This patch updates NUMA counters to a fixed size of (MAX_S16 - 2) and deals >>>> with global counter update using different threshold size for node page >>>> stats. >>> >>> Again, no numbers. >> >> Compare to vanilla kernel, I don't think it has performance improvement, so >> I didn't post performance data here. >> But, if you would like to see performance gain from enlarging threshold size >> for NUMA stats (compare to the first patch), I will do that later. > > Please do. I would also like to hear _why_ all counters cannot simply > behave same. In other words why we cannot simply increase > stat_threshold? Maybe calculate_normal_threshold needs a better scaling > for larger machines. > Agree. We may consider that. But, unlike NUMA counters which do not effect system decision. We need consider very carefully when increase stat_threshold for all the counters for larger machines. BTW, this is another topic that we may discuss it in different thread.