From: Reinette Chatre <reinette.chatre@intel.com>
To: Fenghua Yu <fenghuay@nvidia.com>, Tony Luck <tony.luck@intel.com>,
"Ben Horgan" <ben.horgan@arm.com>,
James Morse <james.morse@arm.com>,
Dave Martin <Dave.Martin@arm.com>,
Babu Moger <babu.moger@amd.com>,
Drew Fustini <fustini@kernel.org>, Chen Yu <yu.c.chen@intel.com>,
Jinjie Ruan <ruanjinjie@huawei.com>
Cc: Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
Peter Newman <peternewman@google.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v3] arm,x86,fs/resctrl: Generic schema description Proof of Concept
Date: Fri, 20 Nov 2026 12:26:20 -0800 [thread overview]
Message-ID: <5303aae7-7886-42a8-85f7-78f62e538f0a@intel.com> (raw)
In-Reply-To: <cd2b8441-e438-46e2-bc2b-9623d5d6abf2@nvidia.com>
Hi Fenghua,
On 11/20/26 11:48 AM, Fenghua Yu wrote:
>
>
> On 11/19/26 21:04, Reinette Chatre wrote:
>> Hi Everybody,
>>
>> I believe that discussions around resctrl's upcoming support for multiple
>> controls are starting to settle. This RFC aims to capture all the remaining
>> items in implementation as well as documentation. Please point out to me if
>> there is anything I missed.
>>
>> RFC v3 of this PoC can be found at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git branch resctrl/controls_rfc_v3
>>
>> Please refer to the documentation patch for an overview of the planned interface
>> changes as well as user space contracts/expectations:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=95ff9ff7430095cb7264946c944c750315db73d9
>>
>> Remaining opens:
>> ---------------
>> - Ben: I do have a question about the formula used to determine the size of
>> a scalar cache control. Please see patch changelog of:
>> https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v3&id=8695aab0997d5aa60e104374fae9701f51156c18
>> - MPAM only compile tested.
>
> Basic MPAM tests work fine.
>
Thank you very much for testing this. Much appreciated.
This version implements the naming format that Ben pointed out to you in
https://lore.kernel.org/all/10d97df6-ccfc-4025-9773-0ebe7421cbaf@arm.com/
that points to a discussion during RFC v1 of the PoC, which continued in RFC v2
and finally settled there as
https://lore.kernel.org/all/bccb1249-e722-451a-9c75-8aa846713045@intel.com/
In this version, the driver is required to set a scope when creating a new control
and resctrl filesystem constructs the final name. The new naming should "just work"
for features built on top of this. Please let me know where it does not.
Reinette
prev parent reply other threads:[~2026-11-20 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 5:04 Reinette Chatre
2026-11-20 19:48 ` Fenghua Yu
2026-11-20 20:26 ` Reinette Chatre [this message]
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=5303aae7-7886-42a8-85f7-78f62e538f0a@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=fustini@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=ruanjinjie@huawei.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@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
all inboxes | Powered by JetHome®