From: Nico Pache <npache@redhat.com>
To: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xenproject.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, virtualization@lists.linux.dev
Cc: alexander.atanasov@virtuozzo.com, muchun.song@linux.dev,
roman.gushchin@linux.dev, mhocko@kernel.org, kys@microsoft.com,
haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
jgross@suse.com, sstabellini@kernel.org,
oleksandr_tyshchenko@epam.com, akpm@linux-foundation.org,
mst@redhat.com, david@redhat.com, yosry.ahmed@linux.dev,
hannes@cmpxchg.org, nphamcs@gmail.com, chengming.zhou@linux.dev,
kanchana.p.sridhar@intel.com, llong@redhat.com,
shakeel.butt@linux.dev
Subject: [PATCH v2 0/4] track memory used by balloon drivers
Date: Fri, 14 Mar 2025 15:37:53 -0600 [thread overview]
Message-ID: <20250314213757.244258-1-npache@redhat.com> (raw)
This series introduces a way to track memory used by balloon drivers.
Add a NR_BALLOON_PAGES counter to track how many pages are reclaimed by the
balloon drivers. First add the accounting, then updates the balloon drivers
(virtio, Hyper-V, VMware, Pseries-cmm, and Xen) to maintain this counter. The
virtio, Vmware, and pseries-cmm balloon drivers utilize the balloon_compaction
interface to allocate and free balloon pages. Other balloon drivers will have to
maintain this counter manually.
This makes the information visible in memory reporting interfaces like
/proc/meminfo, show_mem, and OOM reporting.
This provides admins visibility into their VM balloon sizes without
requiring different virtualization tooling. Furthermore, this information
is helpful when debugging an OOM inside a VM.
V2 changes:
- Add counter to the balloon_compaction interface
- Dropped patches for virtio and VMware as they use balloon_compaction interface
Tested: virtio_balloon, run stress-ng, inflate balloon, oom prints
Signed-off-by: Nico Pache <npache@redhat.com>
Nico Pache (4):
meminfo: add a per node counter for balloon drivers
balloon_compaction: update the NR_BALLOON_PAGES state
hv_balloon: update the NR_BALLOON_PAGES state
xen: balloon: update the NR_BALLOON_PAGES state
drivers/hv/hv_balloon.c | 2 ++
drivers/xen/balloon.c | 4 ++++
fs/proc/meminfo.c | 2 ++
include/linux/mmzone.h | 1 +
mm/balloon_compaction.c | 2 ++
mm/show_mem.c | 4 +++-
mm/vmstat.c | 1 +
7 files changed, 15 insertions(+), 1 deletion(-)
--
2.48.1
next reply other threads:[~2025-03-14 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 21:37 Nico Pache [this message]
2025-03-14 21:37 ` [PATCH v2 1/4] meminfo: add a per node counter for " Nico Pache
2025-03-15 1:06 ` Andrew Morton
2025-03-17 22:37 ` Nico Pache
2025-03-14 21:37 ` [PATCH v2 2/4] balloon_compaction: update the NR_BALLOON_PAGES state Nico Pache
2025-03-14 21:37 ` [PATCH v2 3/4] hv_balloon: " Nico Pache
2025-03-15 4:09 ` Michael Kelley
2025-03-14 21:37 ` [PATCH v2 4/4] xen: balloon: " Nico Pache
2025-03-18 10:16 ` Jürgen Groß
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=20250314213757.244258-1-npache@redhat.com \
--to=npache@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.atanasov@virtuozzo.com \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hannes@cmpxchg.org \
--cc=jgross@suse.com \
--cc=kanchana.p.sridhar@intel.com \
--cc=kys@microsoft.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llong@redhat.com \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=sstabellini@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=wei.liu@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yosry.ahmed@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox