linux-kernel - Re: [patch -mm] mm, vmstat: suppress pcp stats for unpopulated zones in zoneinfo

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: <20170306141142.f3b22bc0ba43814f546bf3a0@linux-foundation.org>
Date:   Mon, 6 Mar 2017 14:11:42 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     David Rientjes <rientjes@...gle.com>
Cc:     Anshuman Khandual <khandual@...ux.vnet.ibm.com>,
        Vlastimil Babka <vbabka@...e.cz>,
        Mel Gorman <mgorman@...hsingularity.net>,
        Johannes Weiner <hannes@...xchg.org>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [patch -mm] mm, vmstat: suppress pcp stats for unpopulated
 zones in zoneinfo

On Mon, 6 Mar 2017 14:03:32 -0800 (PST) David Rientjes <rientjes@...gle.com> wrote:

> After "mm, vmstat: print non-populated zones in zoneinfo", /proc/zoneinfo 
> will show unpopulated zones.
> 
> The per-cpu pageset statistics are not relevant for unpopulated zones and 
> can be potentially lengthy, so supress them when they are not interesting.
> 
> Also moves lowmem reserve protection information above pcp stats since it 
> is relevant for all zones per vm.lowmem_reserve_ratio.

Well it's not strictly back-compatible, but /proc/zoneinfo is such a
mess that parsers will be few and hopefully smart enough to handle
this.

btw,

  pagesets
    cpu: 0
              count: 118
              high:  186
              batch: 31
  vm stats threshold: 72
    cpu: 1
              count: 53
              high:  186
              batch: 31
  vm stats threshold: 72

Should the "vm stats threshold" thing be indented further?

Do we need to print it out N times anyway?  Can different CPUs have
different values?