From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 8E30B1FF16B for ; Tue, 15 Jul 2025 16:31:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B52413FBA2; Tue, 15 Jul 2025 16:32:25 +0200 (CEST) From: Aaron Lauterer To: pve-devel@lists.proxmox.com Date: Tue, 15 Jul 2025 16:31:55 +0200 Message-Id: <20250715143218.1548306-12-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.39.5 In-Reply-To: <20250715143218.1548306-1-a.lauterer@proxmox.com> References: <20250715143218.1548306-1-a.lauterer@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.020 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 RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH common v3 2/2] add function to retrieve pressures from cgroup 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: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" From: Folke Gleumes Originally-by: Folke Gleumes [AL: * rebased on current master * merged into single function for generic cgroups * renamed commit to match single generic function ] Signed-off-by: Aaron Lauterer --- Notes: while the read_cgroup_pressure function would fit better into SysFSTools.pm I have kept it in ProcFSTools.pm for now, mainly because we currently don't use ProcFSTools in SysFSTools, and the actual function to parse the contents of the pressure files in in ProcFSTools. If that would not be an issue, we could also move the read_cgroup_pressure function to SysFSTools changes since RFC: * instead of dedicated functions for CTs and VMs we use a more generic for cgroups in general src/PVE/ProcFSTools.pm | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/PVE/ProcFSTools.pm b/src/PVE/ProcFSTools.pm index f342890..f28372b 100644 --- a/src/PVE/ProcFSTools.pm +++ b/src/PVE/ProcFSTools.pm @@ -151,6 +151,17 @@ sub parse_pressure { return $res; } +sub read_cgroup_pressure { + my ($cgroup_path) = @_; + + my $res = {}; + for my $type (qw(cpu memory io)) { + my $stats = parse_pressure("sys/fs/cgroup/${cgroup_path}/${type}.pressure"); + $res->{$type} = $stats if $stats; + } + return $res; +} + sub read_pressure { my $res = {}; foreach my $type (qw(cpu memory io)) { -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel