From: Reinette Chatre <reinette.chatre@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"Wieczor-Retman, Maciej" <maciej.wieczor-retman@intel.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
Shuah Khan <shuah@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH 4/4] selftests/resctrl: Adjust SNC support messages
Date: Thu, 7 Mar 2024 14:39:08 -0800 [thread overview]
Message-ID: <55a55960-8bb1-4ce2-a2c7-68e167da8bcc@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6083AACB10645E41DD3F9639FC202@SJ1PR11MB6083.namprd11.prod.outlook.com>
Hi Tony,
On 3/7/2024 1:14 PM, Luck, Tony wrote:
>> Thinking about it even differently. The goal is to give information
>> to userspace so we need to think about what would help user space?
>> For example, what if there is a file in info that shows
>> which CPUs are associated with each domain?
>
> Reinette,
>
> Interesting idea. That would save users from having to chase through
> /sys/devices/system/cpu/cpu*/cache/index?/* to figure out what the domain
> numbers in schemata files and the mon_data/mon_L3_XX values mean.
>
> May be extra useful for ARM which seems to have big random-looking numbers
> for domains that came out of ACPI tables.
>
> For SNC it would get the user directly to what they probably care about
> (which CPUs are in which domain).
I agree.
>
> So something like this for an SNC 2 system:
>
> $ cat /sys/fs/resctrl/info/L3/cpus
> 0: 0-35,72-107
> 1: 36-71,108-143
>
> $ cat /sys/fs/resctrl/info/L3_MON/cpus
> 0: 0-17,72-89
> 1: 18-35,90-107
> 2: 36-53,108-125
> 3: 54-71,126-143
>
> [maybe there is a better name than "cpus" for this file?]
Thank you for the example. I find that significantly easier to
understand than a single number in a generic "nodes_per_l3_cache".
Especially with potential confusion surrounding inconsistent "nodes"
between allocation and monitoring.
How about domain_cpu_list and domain_cpu_map ?
Reinette
next prev parent reply other threads:[~2024-03-07 22:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 10:38 [PATCH 0/4] SNC support for resctrl selftests Maciej Wieczor-Retman
2024-03-06 10:39 ` [PATCH 1/4] selftests/resctrl: Adjust effective L3 cache size with SNC enabled Maciej Wieczor-Retman
2024-03-06 10:39 ` [PATCH 2/4] selftests/resctrl: SNC support for CMT Maciej Wieczor-Retman
2024-03-08 13:53 ` Ilpo Järvinen
2024-03-08 13:59 ` Ilpo Järvinen
2024-03-13 10:23 ` Maciej Wieczor-Retman
2024-03-06 10:39 ` [PATCH 3/4] selftests/resctrl: SNC support for MBM Maciej Wieczor-Retman
2024-03-08 14:07 ` Ilpo Järvinen
2024-03-13 10:26 ` Maciej Wieczor-Retman
2024-03-06 10:39 ` [PATCH 4/4] selftests/resctrl: Adjust SNC support messages Maciej Wieczor-Retman
2024-03-06 21:54 ` Luck, Tony
2024-03-07 9:25 ` Maciej Wieczor-Retman
2024-03-07 17:18 ` Luck, Tony
2024-03-07 17:41 ` Reinette Chatre
2024-03-07 17:57 ` Luck, Tony
2024-03-07 19:52 ` Reinette Chatre
2024-03-07 21:14 ` Luck, Tony
2024-03-07 22:39 ` Reinette Chatre [this message]
2024-03-07 23:16 ` Tony Luck
2024-03-07 23:41 ` Reinette Chatre
2024-03-08 18:06 ` James Morse
2024-03-08 18:42 ` Tony Luck
2024-03-15 18:02 ` James Morse
2024-03-18 19:15 ` Reinette Chatre
2024-03-18 19:34 ` Luck, Tony
2024-03-18 20:32 ` Reinette Chatre
2024-03-18 20:47 ` Luck, Tony
2024-03-18 21:04 ` Luck, Tony
2024-03-18 21:26 ` Reinette Chatre
2024-03-18 22:00 ` Luck, Tony
2024-03-18 22:43 ` Reinette Chatre
2024-03-18 21:23 ` Reinette Chatre
2024-03-18 22:04 ` Luck, Tony
2024-03-19 21:01 ` Peter Newman
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=55a55960-8bb1-4ce2-a2c7-68e167da8bcc@intel.com \
--to=reinette.chatre@intel.com \
--cc=fenghua.yu@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=shuah@kernel.org \
--cc=tony.luck@intel.com \
/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