[pve-devel] [PATCH 1/5] fix #3593: Added vm core pinning pve-docs

Matthias Heiserer m.heiserer at proxmox.com
Wed Jun 8 16:20:12 CEST 2022


On 08.06.2022 13:54, Daniel Bowder wrote:
> Signed-off-by: Daniel Bowder <daniel at bowdernet.com>
> ---
>   The first patch adds an entry to the qm conf adding a new option: cpuset. The cpuset here is the same cpuset used by the taskset application for pinning a process to a cpu core. This can be found in `man cpuset`, or https://linux.die.net/man/7/cpuset
>   qm.conf.5-opts.adoc | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/qm.conf.5-opts.adoc b/qm.conf.5-opts.adoc
> index a56dc5d..992cd51 100644
> --- a/qm.conf.5-opts.adoc
> +++ b/qm.conf.5-opts.adoc
> @@ -155,6 +155,10 @@ Limit of CPU usage.
>   +
>   NOTE: If the computer has 2 CPUs, it has total of '2' CPU time. Value '0' indicates no CPU limit.
>   
> +`cpuset`: `<string>`::
> +
> +Set of CPU cores to pin the virtual machine processes to. This is a comma sepparated list of numbers or ranges in list format as defined by the Linux man page for cpuset. ( e.g `0,4-6,9` )
typo: "separated"

Personally, I'd prefer something alone the lines of "[..] of numbers in 
the cpuset `List format`", but no hard feelings.

> +
>   `cpuunits`: `<integer> (1 - 262144)` ('default =' `cgroup v1: 1024, cgroup v2: 100`)::
>   
>   CPU weight for a VM. Argument is used in the kernel fair scheduler. The larger the number is, the more CPU time this VM gets. Number is relative to weights of all the other running VMs.




More information about the pve-devel mailing list