From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Wei Xu <weixugc@google.com>
Cc: Sourav Panda <souravpanda@google.com>,
corbet@lwn.net, gregkh@linuxfoundation.org, rafael@kernel.org,
akpm@linux-foundation.org, mike.kravetz@oracle.com,
muchun.song@linux.dev, rppt@kernel.org, david@redhat.com,
rdunlap@infradead.org, chenlinxuan@uniontech.com,
yang.yang29@zte.com.cn, tomas.mudrunka@gmail.com,
bhelgaas@google.com, ivan@cloudflare.com, yosryahmed@google.com,
hannes@cmpxchg.org, shakeelb@google.com,
kirill.shutemov@linux.intel.com, wangkefeng.wang@huawei.com,
adobriyan@gmail.com, vbabka@suse.cz, Liam.Howlett@oracle.com,
surenb@google.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org, willy@infradead.org
Subject: Re: [PATCH v9 1/1] mm: report per-page metadata information
Date: Wed, 13 Mar 2024 18:37:55 -0400 [thread overview]
Message-ID: <CA+CK2bAqdFL-kGmTR8msdy_FSr4Zt7+riJgjdTxX+FN+-M0pLA@mail.gmail.com> (raw)
In-Reply-To: <CAAPL-u-0RekH-ptg9U2pzPJxCAR+jMTxKTZU49LR_isjNkSPWg@mail.gmail.com>
On Mon, Feb 26, 2024 at 1:12 PM Wei Xu <weixugc@google.com> wrote:
>
> On Tue, Feb 20, 2024 at 1:46 PM Sourav Panda <souravpanda@google.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.
>
> /proc/vmstat also has the system-wide nr_memmap and nr_memmap_boot.
> Given that nr_memmap in /proc/vmstat provides the same info (in
> different units) as Memmap in /proc/meminfo, it would be better to
> remove Memmap from /proc/meminfo to avoid duplication and confusion.
There are many items both in meminfo and in vmstat. Given that
/proc/meminfo covers all kmem memory, it is beneficial to keep the
kmem part of memmap in meminfo as another classification item.
Pasha
next prev parent reply other threads:[~2024-03-13 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 21:45 [PATCH v9 0/1] " Sourav Panda
2024-02-20 21:45 ` [PATCH v9 1/1] " Sourav Panda
2024-02-26 18:12 ` Wei Xu
2024-03-13 22:37 ` Pasha Tatashin [this message]
2024-03-13 22:40 ` Pasha Tatashin
2024-03-19 14:25 ` Pasha Tatashin
2024-03-19 21:33 ` Andrew Morton
2024-04-10 23:58 ` David Rientjes
2024-04-11 5:42 ` Sourav Panda
2024-04-12 17:04 ` Pasha Tatashin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+CK2bAqdFL-kGmTR8msdy_FSr4Zt7+riJgjdTxX+FN+-M0pLA@mail.gmail.com \
--to=pasha.tatashin@soleen.com \
--cc=Liam.Howlett@oracle.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=chenlinxuan@uniontech.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=ivan@cloudflare.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=tomas.mudrunka@gmail.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=yang.yang29@zte.com.cn \
--cc=yosryahmed@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox