From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965101AbcFMR0W (ORCPT ); Mon, 13 Jun 2016 13:26:22 -0400 Received: from resqmta-ch2-06v.sys.comcast.net ([69.252.207.38]:47784 "EHLO resqmta-ch2-06v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932111AbcFMR0V (ORCPT ); Mon, 13 Jun 2016 13:26:21 -0400 Date: Mon, 13 Jun 2016 12:26:13 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Mel Gorman cc: Andrew Morton , Linux-MM , Rik van Riel , Vlastimil Babka , Johannes Weiner , LKML Subject: Re: [PATCH 01/27] mm, vmstat: Add infrastructure for per-node vmstats In-Reply-To: <1465495483-11855-2-git-send-email-mgorman@techsingularity.net> Message-ID: References: <1465495483-11855-1-git-send-email-mgorman@techsingularity.net> <1465495483-11855-2-git-send-email-mgorman@techsingularity.net> Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 9 Jun 2016, Mel Gorman wrote: > VM statistic counters for reclaim decisions are zone-based. If the kernel > is to reclaim on a per-node basis then we need to track per-node statistics > but there is no infrastructure for that. The most notable change is that There is node_page_state() so the value of any counter per node is already available. Note that some of the counters (NUMA_xx) for example do not make much sense as per zone counters and are effectively used as per node counters. So the main effect you are looking for is to have the counters stored in the per node structure as opposed to the per zone struct in order to avoid the summing? Doing so duplicates a large amount of code it seems. If you do this then also move over certain counters that have more of a per node use from per zone to per node. Like the NUMA_xxx counters.