From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C0FB8C176E for ; Tue, 16 Jan 2024 14:23:21 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A891836BE6 for ; Tue, 16 Jan 2024 14:22:51 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 16 Jan 2024 14:22:50 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 70D134914D for ; Tue, 16 Jan 2024 14:22:50 +0100 (CET) From: Alexander Zeidler To: pve-devel@lists.proxmox.com Date: Tue, 16 Jan 2024 14:22:39 +0100 Message-Id: <20240116132240.132246-2-a.zeidler@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20240116132240.132246-1-a.zeidler@proxmox.com> References: <20240116132240.132246-1-a.zeidler@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.055 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH docs 2/3] qm: resource limits: revise section cpuunits X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2024 13:23:21 -0000 * restructure sentences minimally * improve section-formatting Signed-off-by: Alexander Zeidler --- qm.adoc | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/qm.adoc b/qm.adoc index 268a635..15aa0fc 100644 --- a/qm.adoc +++ b/qm.adoc @@ -364,17 +364,21 @@ up to use more CPU time than just its virtual CPUs could use. To ensure that a VM never uses more CPU time than vCPUs assigned, set the *cpulimit* to the same value as the total core count. -The second CPU resource limiting setting, *cpuunits* (nowadays often called CPU -shares or CPU weight), controls how much CPU time a VM gets compared to other -running VMs. It is a relative weight which defaults to `100` (or `1024` if the -host uses legacy cgroup v1). If you increase this for a VM it will be -prioritized by the scheduler in comparison to other VMs with lower weight. For -example, if VM 100 has set the default `100` and VM 200 was changed to `200`, -the latter VM 200 would receive twice the CPU bandwidth than the first VM 100. +*cpuuntis* + +With the *cpuunits* option, nowadays often called CPU shares or CPU weight, you +can control how much CPU time a VM gets compared to other running VMs. It is a +relative weight which defaults to `100` (or `1024` if the host uses legacy +cgroup v1). If you increase this for a VM it will be prioritized by the +scheduler in comparison to other VMs with lower weight. + +For example, if VM 100 has set the default `100` and VM 200 was changed to +`200`, the latter VM 200 would receive twice the CPU bandwidth than the first +VM 100. For more information see `man systemd.resource-control`, here `CPUQuota` -corresponds to `cpulimit` and `CPUWeight` corresponds to our `cpuunits` -setting, visit its Notes section for references and implementation details. +corresponds to `cpulimit` and `CPUWeight` to our `cpuunits` setting. Visit its +Notes section for references and implementation details. The third CPU resource limiting setting, *affinity*, controls what host cores the virtual machine will be permitted to execute on. E.g., if an affinity value -- 2.39.2