From: Reinette Chatre <reinette.chatre@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"Moger, Babu" <bmoger@amd.com>, "Babu Moger" <babu.moger@amd.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"paulmck@kernel.org" <paulmck@kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"thuth@redhat.com" <thuth@redhat.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"mario.limonciello@amd.com" <mario.limonciello@amd.com>,
"perry.yuan@amd.com" <perry.yuan@amd.com>,
"seanjc@google.com" <seanjc@google.com>,
"Huang, Kai" <kai.huang@intel.com>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"kan.liang@linux.intel.com" <kan.liang@linux.intel.com>,
"riel@surriel.com" <riel@surriel.com>,
"Li, Xin3" <xin3.li@intel.com>, "xin@zytor.com" <xin@zytor.com>,
"Mehta, Sohil" <sohil.mehta@intel.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"ebiggers@google.com" <ebiggers@google.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"gautham.shenoy@amd.com" <gautham.shenoy@amd.com>,
"Xiaojian.Du@amd.com" <Xiaojian.Du@amd.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"fenghuay@nvidia.com" <fenghuay@nvidia.com>,
"peternewman@google.com" <peternewman@google.com>
Subject: Re: [PATCH v4 0/8] Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE)
Date: Mon, 5 May 2025 10:39:53 -0700 [thread overview]
Message-ID: <e0e72b1c-40bd-4079-be89-3eb2339d893d@intel.com> (raw)
In-Reply-To: <SJ1PR11MB60838694300279E4A0E4506EFC8E2@SJ1PR11MB6083.namprd11.prod.outlook.com>
Hi Tony,
On 5/5/25 10:27 AM, Luck, Tony wrote:
>>> " Non-CPU agent RDT uses the RMID and CLOS tags in the same way that they are used for CPU agents."
>>
>> As I understand AMD uses a single specific (the highest CLOSid supported by L3)
>> CLOS that is then reserved for IO allocation. While both Intel and AMD technically
>> "uses CLOSid", it is done differently, no?
>>
>> Specifically, is this documentation introduced in patch #5 accurate for Intel?
>> + The feature routes the I/O traffic via specific CLOSID reserved
>> + for io_alloc feature. By configuring the CBM (Capacity Bit Mask)
>> + for the CLOSID, users can control the L3 portions available for
>> + I/0 traffic. The reserved CLOSID will be excluded for group creation.
>
> No. Intel doesn't reserve a single CLOS. It allows to assign RMIDs and CLOSids
> for I/O monitoring and control. Different IDs can be assigned to different groups
> of devices (the "grouping" is dependent on h/w routing to devices, not
> assignable by the OS).
How does this work with CDP on Intel? Can CDP be enabled for CPU agents while the
"code" and "data" CLOSids be used for I/O control?
Reinette
next prev parent reply other threads:[~2025-05-05 17:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 22:43 [PATCH v4 0/8] Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Babu Moger
2025-04-21 22:43 ` [PATCH v4 1/8] x86/cpufeatures: Add support for L3 Smart Data Cache Injection Allocation Enforcement Babu Moger
2025-04-21 22:43 ` [PATCH v4 2/8] x86/resctrl: Add SDCIAE feature in the command line options Babu Moger
2025-04-21 22:43 ` [PATCH v4 3/8] x86/resctrl: Detect io_alloc feature Babu Moger
2025-04-21 22:43 ` [PATCH v4 4/8] x86/resctrl: Implement "io_alloc" enable/disable handlers Babu Moger
2025-04-21 22:43 ` [PATCH v4 5/8] x86/resctrl: Add user interface to enable/disable io_alloc feature Babu Moger
2025-04-21 22:43 ` [PATCH v4 6/8] x86/resctrl: Introduce interface to display io_alloc CBMs Babu Moger
2025-04-21 22:43 ` [PATCH v4 7/8] x86/resctrl: Modify rdt_parse_data to pass mode and CLOSID Babu Moger
2025-04-21 22:43 ` [PATCH v4 8/8] x86/resctrl: Introduce interface to modify io_alloc Capacity Bit Masks Babu Moger
2025-05-02 21:20 ` [PATCH v4 0/8] Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Reinette Chatre
2025-05-03 0:53 ` Moger, Babu
2025-05-05 16:22 ` Reinette Chatre
2025-05-05 17:01 ` Luck, Tony
2025-05-05 17:14 ` Reinette Chatre
2025-05-05 17:27 ` Luck, Tony
2025-05-05 17:39 ` Reinette Chatre [this message]
2025-05-05 17:50 ` Luck, Tony
2025-05-05 19:54 ` Moger, Babu
2025-05-05 21:13 ` Reinette Chatre
2025-05-05 22:29 ` Moger, Babu
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=e0e72b1c-40bd-4079-be89-3eb2339d893d@intel.com \
--to=reinette.chatre@intel.com \
--cc=Xiaojian.Du@amd.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=ardb@kernel.org \
--cc=babu.moger@amd.com \
--cc=bmoger@amd.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=fenghuay@nvidia.com \
--cc=gautham.shenoy@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kai.huang@intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=perry.yuan@amd.com \
--cc=peternewman@google.com \
--cc=riel@surriel.com \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=thuth@redhat.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=xin3.li@intel.com \
--cc=xin@zytor.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;
as well as URLs for NNTP newsgroup(s).