linux-kernel - Re: [PATCH v13] mm: report per-page metadata information

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: <20240611153003.9f1b701e0ed28b129325128a@linux-foundation.org>
Date: Tue, 11 Jun 2024 15:30:03 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Sourav Panda <souravpanda@...gle.com>
Cc: corbet@....net, gregkh@...uxfoundation.org, rafael@...nel.org,
 mike.kravetz@...cle.com, muchun.song@...ux.dev, rppt@...nel.org,
 david@...hat.com, rdunlap@...radead.org, chenlinxuan@...ontech.com,
 yang.yang29@....com.cn, tomas.mudrunka@...il.com, bhelgaas@...gle.com,
 ivan@...udflare.com, pasha.tatashin@...een.com, yosryahmed@...gle.com,
 hannes@...xchg.org, shakeelb@...gle.com, kirill.shutemov@...ux.intel.com,
 wangkefeng.wang@...wei.com, adobriyan@...il.com, vbabka@...e.cz,
 Liam.Howlett@...cle.com, surenb@...gle.com, linux-kernel@...r.kernel.org,
 linux-fsdevel@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-mm@...ck.org, willy@...radead.org, weixugc@...gle.com, David Rientjes
 <rientjes@...gle.com>
Subject: Re: [PATCH v13] mm: report per-page metadata information

On Wed,  5 Jun 2024 22:27:51 +0000 Sourav Panda <souravpanda@...gle.com> wrote:

> Today, we do not have any observability of per-page metadata
> and how much it takes away from the machine capacity. Thus,
> we want to describe the amount of memory that is going towards
> per-page metadata, which can vary depending on build
> configuration, machine architecture, and system use.
> 
> This patch adds 2 fields to /proc/vmstat that can used as shown
> below:
> 
> Accounting per-page metadata allocated by boot-allocator:
> 	/proc/vmstat:nr_memmap_boot * PAGE_SIZE
> 
> Accounting per-page metadata allocated by buddy-allocator:
> 	/proc/vmstat:nr_memmap * PAGE_SIZE
> 
> Accounting total Perpage metadata allocated on the machine:
> 	(/proc/vmstat:nr_memmap_boot +
> 	 /proc/vmstat:nr_memmap) * PAGE_SIZE

Under what circumstances do these change?  Only hotplug?

It's nasty, but would it be sufficient to simply emit these numbers
into dmesg when they change?