From: Reinette Chatre <reinette.chatre@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
Peter Newman <peternewman@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
"x86@kernel.org" <x86@kernel.org>
Cc: Shaopeng Tan <tan.shaopeng@fujitsu.com>,
James Morse <james.morse@arm.com>,
Jamie Iles <quic_jiles@quicinc.com>,
Babu Moger <babu.moger@amd.com>,
Randy Dunlap <rdunlap@infradead.org>,
Drew Fustini <dfustini@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
"Wieczor-Retman, Maciej" <maciej.wieczor-retman@intel.com>
Subject: Re: [PATCH v16 0/9] Add support for Sub-NUMA cluster (SNC) systems
Date: Tue, 19 Mar 2024 14:00:39 -0700 [thread overview]
Message-ID: <18ac2a1f-733c-4586-b9d8-d16bb9bfa2fe@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6083B59F32F33C0FFBFCA1BCFC2C2@SJ1PR11MB6083.namprd11.prod.outlook.com>
Hi Tony,
On 3/19/2024 1:31 PM, Luck, Tony wrote:
>> I agree to drop patch #9.
>>
>> The core support for SNC continue to look good to me (I just had a few nitpicks).
>>
>> What remains is the user interface that continues to gather opinions [3]. These new
>> discussions were prompted by user space needing a way to determine if resctrl supports
>> SNC. This started by using the "size" file but thinking about it more user space could
>> also look at whether the number of L3 control domains are different from the number
>> of L3 monitoring domains? I am adding Maciej for his opinion (please also include him
>> in future versions of this series).
>
> Implementing the revised user interface will make significant changes to the
> patches needed to support SNC. Working on them now.
>
> Minor stuff is the that "size" file won't need to change (because summing across
> all SNC domains mean that all of the cache is counted in mon_data/mon_L3_xx/llc_occupancy.
> The new mon_data/mon_L3_xx/mon_NODE_xxllc_occupancy files are the ones limited
> to 1/snc_ways of L3 capacity.
If the "size" file is impacted by this change then I think there is something
wrong with the current series because "size" is intended to mirror the schemata
file that represents the size in bytes that correspond to the bits from schemata -
this monitoring change does not change this relationship.
>
> Major stuff is that we now need both the L3-scoped domain list as well as the NODE
> scoped domain list. So no longer just changing the "mon_scope" field in the L3
> rdt_resource from one value to another.
Here may be opportunity to isolate the SNC layout from the customs. For example, the
extra layers of files only need to be added when knowing SNC is active and the
cache<->node relationships can be determined dynamically on file create and
read instead of creating new lists and data structures to try and describe it
as part of the architecture.
>
> I'll maybe have a draft set of patches in a day or two.
I was actually hoping to get a discussion started about what folks really want
to see instead of you implementing yet another new feature that folks may
disagree with.
Reinette
next prev parent reply other threads:[~2024-03-19 21:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 21:42 [PATCH v16 0/9] Add support for Sub-NUMA cluster (SNC) systems Tony Luck
2024-03-12 21:42 ` [PATCH v16 1/9] x86/resctrl: Prepare for new domain scope Tony Luck
2024-03-19 17:49 ` Reinette Chatre
2024-03-12 21:42 ` [PATCH v16 2/9] x86/resctrl: Prepare to split rdt_domain structure Tony Luck
2024-03-12 21:42 ` [PATCH v16 3/9] x86/resctrl: Prepare for different scope for control/monitor operations Tony Luck
2024-03-19 17:50 ` Reinette Chatre
2024-03-12 21:42 ` [PATCH v16 4/9] x86/resctrl: Split the rdt_domain and rdt_hw_domain structures Tony Luck
2024-03-12 21:42 ` [PATCH v16 5/9] x86/resctrl: Add node-scope to the options for feature scope Tony Luck
2024-03-12 21:42 ` [PATCH v16 6/9] x86/resctrl: Introduce snc_nodes_per_l3_cache Tony Luck
2024-03-12 21:42 ` [PATCH v16 7/9] x86/resctrl: Sub NUMA Cluster detection and enable Tony Luck
2024-03-12 21:42 ` [PATCH v16 8/9] x86/resctrl: Update documentation with Sub-NUMA cluster changes Tony Luck
2024-03-12 21:42 ` [PATCH v16 9/9] x86/resctrl: Add info files to show mappings from domains to lists of cpus Tony Luck
2024-03-19 17:51 ` [PATCH v16 0/9] Add support for Sub-NUMA cluster (SNC) systems Reinette Chatre
2024-03-19 20:31 ` Luck, Tony
2024-03-19 21:00 ` Reinette Chatre [this message]
2024-03-20 15:21 ` Maciej Wieczor-Retman
2024-03-20 15:50 ` Reinette Chatre
2024-03-20 16:27 ` Maciej Wieczor-Retman
2024-03-21 7:51 ` Maciej Wieczor-Retman
2024-03-21 16:51 ` Luck, Tony
2024-03-22 14:57 ` Maciej Wieczor-Retman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18ac2a1f-733c-4586-b9d8-d16bb9bfa2fe@intel.com \
--to=reinette.chatre@intel.com \
--cc=babu.moger@amd.com \
--cc=corbet@lwn.net \
--cc=dfustini@baylibre.com \
--cc=fenghua.yu@intel.com \
--cc=james.morse@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=patches@lists.linux.dev \
--cc=peternewman@google.com \
--cc=quic_jiles@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tan.shaopeng@fujitsu.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox