mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Fenghua Yu <fenghuay@nvidia.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: Mon, 10 Aug 2026 13:24:59 +0800	[thread overview]
Message-ID: <81824b51-7407-465a-b3c7-9e39d1523be3@intel.com> (raw)
In-Reply-To: <e9934d87-43e3-45fa-bd9f-9f4963c49d4f@nvidia.com>

Hi Fenghua,

On 8/10/2026 11:25 AM, Fenghua Yu wrote:
> 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 

Yes, this is also my understanding.

> 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 legacy MB, it is currently percentage-based with a valid range of
[1, 100]. Userspace might still want to write using percentage-based
values to maintain backward compatibility.

The native MB control, on the other hand, may have a valid range of
[1, 255]. Therefore, a mapping is required to convert user-provided[1, 100]
  to [1, 255] before writing to the underlying hardware.

> 
> 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?
> 

My understanding is that all of them will be written to the same value,
which has been mapped from [1, 100] to [1, 255].
According to the change:
https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git/commit/?h=resctrl/controls_rfc_v2.1&id=2b4fa1beb03848555090a4e8a3d2bb80524e0478
list_for_each_entry(em_ctrl, &ctrl->emulated_by, entry) {
	//every domain for each emulating controller will write the same value
}

thanks,
Chenyu

  reply	other threads:[~2026-08-10  5:25 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  5:26 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-11  4:06                   ` Reinette Chatre
2026-08-11 14:59                     ` Babu Moger
2026-08-11 15:30                       ` Reinette Chatre
2026-08-11 16:09                         ` Babu Moger
2026-08-24 14:40                 ` Ben Horgan
2026-08-24 18:07                   ` Reinette Chatre
2026-08-25 15:20                     ` Ben Horgan
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-11  3:49         ` Chen, Yu C
2026-08-13 13:59           ` Chen Yu
2026-08-13 15:19             ` Reinette Chatre
2026-08-18 16:02               ` Chen Yu
2026-08-18 17:10                 ` Reinette Chatre
2026-09-14  2:49         ` Chen Yu
2026-09-18 23:11           ` Reinette Chatre
2026-09-21  5:13             ` Chen, Yu C
2026-09-21 15:01               ` Reinette Chatre
2026-09-22  3:19                 ` Chen, Yu C
2026-09-21 16:21               ` Luck, Tony
2026-08-10  2:55 ` Fenghua Yu
2026-08-10  3:02   ` Chen, Yu C
2026-08-10  3:25     ` Fenghua Yu
2026-08-10  5:24       ` Chen, Yu C [this message]
2026-08-10 15:53   ` Reinette Chatre
2026-08-17 15:09     ` Reinette Chatre
2026-09-11 10:09     ` Ben Horgan
2026-09-18 22:47       ` Reinette Chatre
2026-09-21 10:22         ` Ben Horgan
2026-09-21 16:06           ` Reinette Chatre
2026-09-21 16:53             ` Ben Horgan
2026-09-23 15:28               ` Reinette Chatre
2026-09-24 14:38                 ` Ben Horgan
2026-09-21 13:56 ` [RFC PATCH 0/3] Suggestions for cache scalar controls Ben Horgan
2026-09-21 13:57   ` [RFC PATCH 1/3] fs/resctrl: Add schema_name to struct resctrl_ctrl Ben Horgan
2026-09-22 20:15     ` Drew Fustini
2026-09-23  9:05       ` Ben Horgan
2026-09-21 13:57   ` [RFC PATCH 2/3] fs/resctrl: Use correct schema name in bw_validate() last_cmd_status messages Ben Horgan
2026-09-21 13:57   ` [RFC PATCH 3/3] fs/resctrl: display size for scalar cache controls Ben Horgan
2026-09-21 14:08   ` [RFC PATCH 0/3] Suggestions for cache scalar controls Ben Horgan
2026-09-22 20:26   ` Drew Fustini

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=81824b51-7407-465a-b3c7-9e39d1523be3@intel.com \
    --to=yu.c.chen@intel.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=fenghuay@nvidia.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 \
    /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®