From: Fenghua Yu <fenghuay@nvidia.com>
To: "Chen, Yu C" <yu.c.chen@intel.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>,
Dave Martin <Dave.Martin@arm.com>,
James Morse <james.morse@arm.com>,
Tony Luck <tony.luck@intel.com>, Ben Horgan <ben.horgan@arm.com>,
Babu Moger <babu.moger@amd.com>,
Drew Fustini <fustini@kernel.org>,
Reinette Chatre <reinette.chatre@intel.com>,
"chen.yu@linux.dev" <chen.yu@linux.dev>
Subject: Re: [RFC v2] arm,x86,fs/resctrl: Generic schema description Proof of Concept
Date: Sun, 9 Aug 2026 20:25:18 -0700 [thread overview]
Message-ID: <e9934d87-43e3-45fa-bd9f-9f4963c49d4f@nvidia.com> (raw)
In-Reply-To: <e8a667f1-60ec-4b9f-9093-30341d8bffe7@intel.com>
Hi, Chen,
On 8/9/26 20:02, Chen, Yu C wrote:
> Hi Fenghua,
> On 8/10/2026 10:55 AM, Fenghua Yu wrote:
>
> [ ... ]
>
>> struct resctrl_ctrl {
>> ...
>> struct list_head emulated_by;
>> };
>>
>> Does this mean a legacy resctrl control can be emulated by a few
>> resctrl controls (which is stored in the list)?
>>
>> e.g. legacy MB control can be emulated by a few controls? I thought
>> "MB:" line is emulated by only one native control. e.g. "MB:" line is
>> emulated by "MB_NODE:" line.
>>
>
> If I understand correctly, for region-aware RDT, the legacy MB control may
> be emulated collectively by region0_control, region1_control, ...,
> regionN_control.
> In the original definition, MB represents the traffic that misses the L3
> cache and
> is refilled from all sources, which could include DRAM (region0), CXL
> (region1),
> and others.
I may misunderstand "emulation" concept here.
I was thinking emulation mode is for backward compatibility, i.e. a
native MB control is emulating "MB:" line: writing and reading both
lines are same. So legacy user app won't be broken on new control.
For a list of resctrl controls (region0_control, region1_control, etc),
which one is for legacy "MB:" control so that reading/wring the control
is same as writing/reading "MB:"line?
Thanks.
-Fenghua
next prev parent reply other threads:[~2026-08-10 3:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 5:26 [RFC v2] arm,x86,fs/resctrl: Generic schema description Proof of Concept Reinette Chatre
2026-08-05 16:59 ` Ben Horgan
2026-08-05 23:57 ` Reinette Chatre
2026-08-06 17:04 ` Luck, Tony
2026-08-06 17:11 ` Reinette Chatre
2026-08-07 14:14 ` Moger, Babu
2026-08-07 15:35 ` Reinette Chatre
2026-08-07 18:33 ` Moger, Babu
2026-08-07 22:53 ` Reinette Chatre
2026-08-10 18:52 ` Babu Moger
2026-08-07 15:35 ` Chen, Yu C
2026-08-07 17:57 ` Moger, Babu
2026-08-10 2:05 ` Chen, Yu C
2026-08-10 15:53 ` Reinette Chatre
2026-08-10 17:23 ` Chen, Yu C
2026-08-10 18:09 ` Reinette Chatre
2026-08-10 2:55 ` Fenghua Yu
2026-08-10 3:02 ` Chen, Yu C
2026-08-10 3:25 ` Fenghua Yu [this message]
2026-08-10 5:24 ` Chen, Yu C
2026-08-10 15:53 ` 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=e9934d87-43e3-45fa-bd9f-9f4963c49d4f@nvidia.com \
--to=fenghuay@nvidia.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=chen.yu@linux.dev \
--cc=dave.hansen@linux.intel.com \
--cc=fustini@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=reinette.chatre@intel.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