From: Reinette Chatre <reinette.chatre@intel.com>
To: Peter Newman <peternewman@google.com>, Rex Nie <rex.nie@jaguarmicro.com>
Cc: <james.morse@arm.com>, "x86@kernel.org" <x86@kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
Babu Moger <babu.moger@amd.com>, Borislav Petkov <bp@alien8.de>,
<fenghua.yu@intel.com>, <ilpo.jarvinen@linux.intel.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: 32bit resctrl? (was Re: [PATCH v2] fs/resctrl: fix domid loss precision issue)
Date: Thu, 14 Mar 2024 17:51:52 -0700 [thread overview]
Message-ID: <3ce123c2-3e04-4ff0-99f3-bd402a47ecb8@intel.com> (raw)
In-Reply-To: <CALPaoChnAt9+2=iVzpownX-bN+mb3Ujn_C=_QS2qsAph=LPSiA@mail.gmail.com>
On 3/14/2024 5:04 PM, Peter Newman wrote:
> On Thu, Mar 14, 2024 at 8:25 AM Reinette Chatre
> <reinette.chatre@intel.com> wrote:
>>
>> +x86 maintainers, Tony, Babu, Peter
>>
>> Hi Everybody,
>>
>> On 3/12/2024 12:53 AM, Rex Nie wrote:
>>> Below statement from mkdir_mondata_subdir function will loss precision,
>>> because it assigns int to 14 bits bitfield.
>>> priv.u.domid = d->id;
>>>
>>> On some platforms(e.g.,x86), the max cache_id is the amount of L3 caches,
>>> so it is not in the range of 0x3fff. But some platforms use higher
>>> cache_id, e.g., arm uses cache_id as locator for cache MSC. This will
>>> cause below issue if cache_id > 0x3fff likes:
>>> /sys/fs/resctrl/mon_groups/p1/mon_data/mon_L3_1048564 # cat llc_occupancy
>
> This domain ID seems unreadable in decimal and I'm wondering whether
> it's the best value to use to identify the domain. Does this system
> have over 1 million L3 domains?
I propose that Rex includes the information about Arm's cache IDs [1]
in future changelogs.
Reinette
[1] https://lore.kernel.org/lkml/KL1PR0601MB577303C9D0B1247436BB06F8E6242@KL1PR0601MB5773.apcprd06.prod.outlook.com/
next prev parent reply other threads:[~2024-03-15 0:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 7:53 [PATCH v2] fs/resctrl: fix domid loss precision issue Rex Nie
2024-03-14 15:25 ` 32bit resctrl? (was Re: [PATCH v2] fs/resctrl: fix domid loss precision issue) Reinette Chatre
2024-03-15 0:04 ` Peter Newman
2024-03-15 0:51 ` Reinette Chatre [this message]
2024-03-15 1:21 ` 答复: " Rex Nie
2024-03-15 0:56 ` Rex Nie
2024-03-15 16:17 ` Moger, Babu
2024-03-15 16:56 ` Peter Newman
2024-03-15 18:00 ` James Morse
2024-03-15 22:42 ` Reinette Chatre
2024-03-18 18:27 ` James Morse
2024-03-15 23:32 ` Thomas Gleixner
2024-03-16 0:08 ` Luck, Tony
2024-03-16 0:20 ` Reinette Chatre
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=3ce123c2-3e04-4ff0-99f3-bd402a47ecb8@intel.com \
--to=reinette.chatre@intel.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=rex.nie@jaguarmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.