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 4BB1D712A7 for ; Wed, 8 Jun 2022 13:55:24 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 426D17724 for ; Wed, 8 Jun 2022 13:54:54 +0200 (CEST) Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 6F5907718 for ; Wed, 8 Jun 2022 13:54:53 +0200 (CEST) Received: by mail-pg1-x532.google.com with SMTP id 129so18682714pgc.2 for ; Wed, 08 Jun 2022 04:54:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bowdernet.com; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=PxvsGfis8mT77MxgS6Utfx9ePYAnKMkVrnWNFTE4Daw=; b=HCEwWRgQt11pOX5jllowN3EBZ/ShPz5f5Fj0cghZD+X3zuEGC3M16v09lpSkvhtuR3 ACUkyrdVpTMSMxxTfWICNOaKoyPUCYGHpfUwPDn2QFUm8xsYHk5zwvzuygotkZX1U66r imtErVUzKSU3KEBg9+MN5Bqxhh4Ox7jqrA6ab+SMXNiQXduy/UspR+j1eY0x3+r1sCoH SzoLeUZS6Gkjhg4U204PmKFtQntyHXp4MWUXAHTCKhQoGbOuruzFc3zgdmRM1NmgDBXf 6NSmcqAvTlRM8yZhtQCmpFBWqJevkyWFhTnZJIDDEpHt5WJR6tXsDqaZ6j/rF9+hCRj5 BVFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=PxvsGfis8mT77MxgS6Utfx9ePYAnKMkVrnWNFTE4Daw=; b=4MZLpqMLQnz5aB8yGEP4IDyUAnqoXg3NS/xCzoBqJkMHdWuzCibZjC3qu5obXLnIGc eUJ8mi8lEBHR+H1I1iGKAk0WUa/GgP4/1mgbKVCknueAMtokpVIRqjnR96DFdYflN2AT U85JC5sd4XP7Cyphn/B3XvSpskqKbMOFR9l3OEsfjbB7Ce81PiwHPARmxHB9LP/yFe6u H5Omx677/50ZvX8LCpUolSaP5McFrk2/PBLQAQfy99qnj1NQ4hjvNa9OVD8hUANpIFwK 8UL56Ewilvfbqgi4S9rty9WtUEIWblol8fY61isOw+WRiIeGS9kn8diMCAshEecn2jym gZKA== X-Gm-Message-State: AOAM533Int7AZAkB543aG//GuMzWGDRWFGmSTWwEGoBxnwlmNAxfvSa4 HpaaMbNG+MCNcNrADcx3ddNC9HP2IH2fBuR9 X-Google-Smtp-Source: ABdhPJwgzRELdm5ykC0PWhtqSvfhThJuygOu0xVkTS4wYHH4N6a+r1HAHXeo2P4bUxd4eFUlXlVEzA== X-Received: by 2002:a63:7c0f:0:b0:3fc:f127:c41e with SMTP id x15-20020a637c0f000000b003fcf127c41emr27496840pgc.55.1654689285896; Wed, 08 Jun 2022 04:54:45 -0700 (PDT) Received: from pve-dev.dbnet.in (c-24-19-168-226.hsd1.wa.comcast.net. [24.19.168.226]) by smtp.gmail.com with ESMTPSA id t6-20020a654b86000000b003fba6db1b50sm14902820pgq.85.2022.06.08.04.54.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Jun 2022 04:54:45 -0700 (PDT) From: Daniel Bowder To: pve-devel@lists.proxmox.com Cc: Daniel Bowder Date: Wed, 8 Jun 2022 04:54:24 -0700 Message-Id: <20220608115428.250668-2-daniel@bowdernet.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20220608115428.250668-1-daniel@bowdernet.com> References: <20220608115428.250668-1-daniel@bowdernet.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust 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 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [die.net, bowdernet.com] X-Mailman-Approved-At: Wed, 08 Jun 2022 14:30:46 +0200 Subject: [pve-devel] [PATCH 1/5] fix #3593: Added vm core pinning pve-docs 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: Wed, 08 Jun 2022 11:55:24 -0000 Signed-off-by: Daniel Bowder --- 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`: ``:: + +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` ) + `cpuunits`: ` (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. -- 2.30.2