linux-kernel - Re: [PATCH v8 1/1] 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: <CAJuCfpHF=yxV9+=pUo+5DwSjvF=r2y7A9_8LHsUGUSoP7EUNXA@mail.gmail.com>
Date: Thu, 15 Feb 2024 16:39:50 -0800
From: Suren Baghdasaryan <surenb@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Sourav Panda <souravpanda@...gle.com>, 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, 
	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
Subject: Re: [PATCH v8 1/1] mm: report per-page metadata information

On Thu, Feb 15, 2024 at 4:14 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Wed, 14 Feb 2024 14:57:40 -0800 Sourav Panda <souravpanda@...gle.com> wrote:
>
> > Adds two new per-node fields, namely nr_memmap and nr_memmap_boot,
> > to /sys/devices/system/node/nodeN/vmstat and a global Memmap field
> > to /proc/meminfo. This information can be used by users to see how
> > much memory is being used by per-page metadata, which can vary
> > depending on build configuration, machine architecture, and system
> > use.
>
> Would this information be available by the proposed memory
> allocation profiling?

Well, not without jumping through the hoops. You would need to find
the places in the source code where all this matadata is allocated and
find the appropriate records inside /proc/allocinfo file.

>
> https://lkml.kernel.org/r/20240212213922.783301-1-surenb@google.com