From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 959A91FF37F for ; Thu, 18 Apr 2024 15:33:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3BE181D621; Thu, 18 Apr 2024 15:33:30 +0200 (CEST) Message-ID: <571770cca597a266fb2ae76b1f5cfff41f03e4ed.camel@proxmox.com> From: Alexander Zeidler To: Aaron Lauterer , Proxmox VE development discussion Date: Thu, 18 Apr 2024 15:32:52 +0200 In-Reply-To: <4e5145ba-abdc-499c-a748-027a0306d773@proxmox.com> References: <20240418091650.51366-1-a.zeidler@proxmox.com> <20240418091650.51366-6-a.zeidler@proxmox.com> <4e5145ba-abdc-499c-a748-027a0306d773@proxmox.com> User-Agent: Evolution 3.46.4-2 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.089 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 Subject: Re: [pve-devel] [PATCH manager 6/7] report: add info about (un)used memory slots 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" On Thu, 2024-04-18 at 12:16 +0200, Aaron Lauterer wrote: > I am not sure how often we actually need that information as it can add > quite a bit of additional lines in the report in larger machines with > many memory slots. Good point. So in this case we could simply compact the output by counting, without loosing any information: # dmidecode -t 16,17 | grep -P "^\t(Max[^:]*city|Size|Part)" | sed -Ez "s/\n(\tP[^\n]*)/\1/g" | sort | uniq -c 1 Maximum Capacity: 2 TB 4 Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1 4 Size: No Module Installed > It might be better to keep that command in a cheatsheet to ask for it if > actually needed instead of polluting the report :) > > On 2024-04-18 11:16, Alexander Zeidler wrote: > > * to see if a RAM upgrade is slot/capacity-wise possible > > * to spot added/replaced RAM that may now be causing issues > > > > Maximum Capacity: 2 TB > > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1 > > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1 > > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1 > > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1 > > Size: No Module Installed > > Size: No Module Installed > > Size: No Module Installed > > Size: No Module Installed _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel