linux-kernel - Re: [PATCH 01/27] mm, vmstat: Add infrastructure for per-node vmstats

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.20.1606131208110.25027@east.gentwo.org>
Date:	Mon, 13 Jun 2016 12:26:13 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Mel Gorman <mgorman@...hsingularity.net>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux-MM <linux-mm@...ck.org>, Rik van Riel <riel@...riel.com>,
	Vlastimil Babka <vbabka@...e.cz>,
	Johannes Weiner <hannes@...xchg.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 01/27] mm, vmstat: Add infrastructure for per-node
 vmstats

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.