Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 03E7CC64EC7 for ; Tue, 28 Feb 2023 17:12:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229705AbjB1RMg (ORCPT ); Tue, 28 Feb 2023 12:12:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38122 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229451AbjB1RMd (ORCPT ); Tue, 28 Feb 2023 12:12:33 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 6B496196B8; Tue, 28 Feb 2023 09:12:32 -0800 (PST) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5961AC14; Tue, 28 Feb 2023 09:13:15 -0800 (PST) Received: from [10.1.196.177] (eglon.cambridge.arm.com [10.1.196.177]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 0938D3F881; Tue, 28 Feb 2023 09:12:28 -0800 (PST) Message-ID: Date: Tue, 28 Feb 2023 17:12:23 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: [PATCH 0/7] x86/resctrl: Add support for Sub-NUMA cluster (SNC) systems Content-Language: en-GB To: Tony Luck , Fenghua Yu , Reinette Chatre , Peter Newman , Jonathan Corbet , x86@kernel.org Cc: Shaopeng Tan , Jamie Iles , Babu Moger , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, patches@lists.linux.dev References: <20230126184157.27626-1-tony.luck@intel.com> From: James Morse In-Reply-To: <20230126184157.27626-1-tony.luck@intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tony, On 26/01/2023 18:41, Tony Luck wrote: > Intel server systems starting with Skylake support a mode that logically > partitions each socket. E.g. when partitioned two ways, half the cores, > L3 cache, and memory controllers are allocated to each of the partitions. > This may reduce average latency to access L3 cache and memory, with the > tradeoff that only half the L3 cache is available for subnode-local memory > access. I couldn't find a description of what happens to the CAT bitmaps or counters. Presumably the CAT bitmaps are duplicated, so each cluster has its own set, and the counters aren't - so software has to co-ordinate the use of RMID across the CPUs? How come cacheinfo isn't modified to report the L3 partitions as separate caches? Otherwise user-space would assume the full size of the cache is available on any of those CPUs. This would avoid an ABI change in resctrl (domain is now the numa node), leaving only the RMID range code. Thanks, James