From: SeongJae Park <sj@kernel.org>
To: Hao Ge <hao.ge@linux.dev>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
linux-mm@kvack.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/balloon: expose per-node balloon pages in node meminfo
Date: Fri, 8 May 2026 18:07:28 -0700 [thread overview]
Message-ID: <20260509010728.84832-1-sj@kernel.org> (raw)
In-Reply-To: <20260508094736.142467-1-hao.ge@linux.dev>
On Fri, 8 May 2026 17:47:36 +0800 Hao Ge <hao.ge@linux.dev> wrote:
> Commit 835de37603ef ("meminfo: add a per node counter for balloon
> drivers") added NR_BALLOON_PAGES and exposed it in /proc/meminfo.
> However, the per-node view at /sys/devices/system/node/nodeX/meminfo
> was not updated, even though the counter is already tracked per-node.
>
> Add it to node_read_meminfo() so users can see balloon usage per
> NUMA node without having to parse the raw vmstat file.
Makes sense to me.
>
> Signed-off-by: Hao Ge <hao.ge@linux.dev>
Acked-by: SeongJae Park <sj@kernel.org>
> ---
> v2: Move Balloon field after Unaccepted to match /proc/meminfo ordering
> (suggested by David Hildenbrand)
Adding a link to previous revision [1] would be nice.
[1] https://docs.kernel.org/process/submitting-patches.html#commentary
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-05-09 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 9:47 [PATCH v2] mm/balloon: expose per-node balloon pages in node meminfo Hao Ge
2026-05-08 10:57 ` David Hildenbrand (Arm)
2026-05-08 18:31 ` Andrew Morton
2026-05-09 1:14 ` Hao Ge
2026-05-09 1:07 ` SeongJae Park [this message]
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=20260509010728.84832-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hao.ge@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=virtualization@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.