From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server] fix #6935: vmstatus: use CGroup for host memory usage
Date: Wed, 14 Jan 2026 14:34:57 +0100 [thread overview]
Message-ID: <176839769262.234577.9494911099056664280.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251128103639.446372-1-f.gruenbichler@proxmox.com>
On Fri, 28 Nov 2025 11:36:34 +0100, Fabian Grünbichler wrote:
> after a certain amount of KSM sharing, PSS lookups become prohibitively
> expensive. instead of reverting to the old broken method, simply use the
> cgroup's memory usage as `memhost` value.
>
> this does not account for merged pages because of KSM anymore.
>
> I benchmarked this with 4 VMs running with different levels of KSM sharing. in
> the output below, "merged pages" refers to the contents of
> /proc/$pid/ksm_merging_pages, the extract_* benchmark runs refer to four
> different variants of extracting memory usage, with the actual extraction part
> running 1000x in a loop for each run to amortize perl/process setup costs,
> qm_status_stock is `qm status $vmid --verbose`, and qm_status_pateched is `perl
> -I./src/PVE ./src/bin/qm status $vmid --verbose` with this patch applied.
>
> [...]
Applied, thanks! Added a follow-up to improve the descriptions for the
'mem' and 'memhost' properties as Fabian suggested at the end of the
discussion of the RFC version.
[1/1] fix #6935: vmstatus: use CGroup for host memory usage
commit: 551c0078de6c2986b75a5db589db881723207624
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-14 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 10:36 [pve-devel] " Fabian Grünbichler
2025-12-17 9:36 ` Fabian Grünbichler
2026-01-09 12:04 ` Fabian Grünbichler
2026-01-14 13:34 ` Fiona Ebner [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=176839769262.234577.9494911099056664280.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.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