From: "Daniel Kral" <d.kral@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] document hugepages option
Date: Thu, 28 Aug 2025 15:26:41 +0200 [thread overview]
Message-ID: <DCE3FX4R53ZV.1RSGBZANX7Z6K@proxmox.com> (raw)
In-Reply-To: <20250828124933.338289-1-m.sandoval@proxmox.com>
On Thu Aug 28, 2025 at 2:49 PM CEST, Maximiliano Sandoval wrote:
> Given that there is no 0 enum, we remove the word "disabled" from the
> docs. We also document that the unit is MiB.
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> src/PVE/QemuServer.pm | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/src/PVE/QemuServer.pm b/src/PVE/QemuServer.pm
> index f263fedb..9d2bba71 100644
> --- a/src/PVE/QemuServer.pm
> +++ b/src/PVE/QemuServer.pm
> @@ -442,7 +442,10 @@ EODESC
> hugepages => {
> optional => 1,
> type => 'string',
> - description => "Enable/disable hugepages memory.",
> + description =>
> + "Enables hugepages memory.\n\nSets the size of hugepages in MiBs. If the value "
> + . "is set to 'any' then 1 GiB hugepages will be used if possible, "
> + . "otherwise the size will fall back to 2 MiB.",
> enum => [qw(any 2 1024)],
> },
> keephugepages => {
As discussed off-list, it might be nice to have a 'off' option, as users
might not come to the conclusion that hugepages can only be disabled by
deleting the property from the config, but the change in description
definitely clarifies what the values mean here, so LGTM.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-08-28 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 12:49 Maximiliano Sandoval
2025-08-28 13:26 ` Daniel Kral [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=DCE3FX4R53ZV.1RSGBZANX7Z6K@proxmox.com \
--to=d.kral@proxmox.com \
--cc=pve-devel-bounces@lists.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