From: "Moger, Babu" <babu.moger@amd.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
corbet@lwn.net, tony.luck@intel.com, Dave.Martin@arm.com,
james.morse@arm.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com
Cc: x86@kernel.org, hpa@zytor.com, akpm@linux-foundation.org,
paulmck@kernel.org, rostedt@goodmis.org, Neeraj.Upadhyay@amd.com,
david@redhat.com, arnd@arndb.de, fvdl@google.com,
seanjc@google.com, thomas.lendacky@amd.com,
pawan.kumar.gupta@linux.intel.com, yosry.ahmed@linux.dev,
sohil.mehta@intel.com, xin@zytor.com, kai.huang@intel.com,
xiaoyao.li@intel.com, peterz@infradead.org, me@mixaill.net,
mario.limonciello@amd.com, xin3.li@intel.com,
ebiggers@google.com, ak@linux.intel.com,
chang.seok.bae@intel.com, andrew.cooper3@citrix.com,
perry.yuan@amd.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 08/10] fs/resctrl: Introduce interface to display io_alloc CBMs
Date: Mon, 4 Aug 2025 13:14:36 -0500 [thread overview]
Message-ID: <4efddbf1-1e98-4ee5-8057-7b3ce5adbec2@amd.com> (raw)
In-Reply-To: <7050592d-6c2c-40ea-a3c5-3e7fcf76c3dc@intel.com>
Hi Reinette,
On 7/21/25 18:42, Reinette Chatre wrote:
> Hi Babu,
>
> On 7/10/25 10:16 AM, Babu Moger wrote:
>> The io_alloc feature in resctrl enables system software to configure
>> the portion of the cache allocated for I/O traffic.
>>
>> Add "io_alloc_cbm" resctrl file to display CBMs (Capacity Bit Mask) o
>> fio_alloc feature.
>
> "o fio_alloc" -> "of the io_alloc"
>
Sure.
>>
>> The CBM interface file io_alloc_cbm will reside in the info directory
>
> "will reside" -> "resides"
>
Sure.
>> (e.g., /sys/fs/resctrl/info/L3/). Displaying the resource name is not
>> necessary. Pass the resource name to show_doms() and print it only if
>> the name is valid. For io_alloc, pass NULL to suppress printing the
>> resource name.
>>
>> When CDP is enabled, io_alloc routes traffic using the highest CLOSID
>> associated with an L3CODE resource. However, CBMs can be accessed via
>> either L3CODE or L3DATA resources.
>
> Seems like something is missing here since this is motivation for a behavior
> but no mention of the behavior being motivated. Also please use imperative tone.
Sure. Added motivation for this.
>
>>
>> Signed-off-by: Babu Moger <babu.moger@amd.com>
>> ---
>
> ...
>
>> ---
>> Documentation/filesystems/resctrl.rst | 18 +++++++++++
>> fs/resctrl/ctrlmondata.c | 8 +++--
>> fs/resctrl/internal.h | 2 ++
>> fs/resctrl/rdtgroup.c | 43 ++++++++++++++++++++++++++-
>> 4 files changed, 67 insertions(+), 4 deletions(-)
>>
>> diff --git a/Documentation/filesystems/resctrl.rst b/Documentation/filesystems/resctrl.rst
>> index 189c1ccb92d6..c22a9dd667cd 100644
>> --- a/Documentation/filesystems/resctrl.rst
>> +++ b/Documentation/filesystems/resctrl.rst
>> @@ -176,6 +176,24 @@ related to allocation:
>> When CDP is enabled, io_alloc routes I/O traffic using the highest
>> CLOSID allocated for the instruction cache (L3CODE).
>>
>> +"io_alloc_cbm":
>> + CBMs(Capacity Bit Masks) that describe the portions of cache instances
>> + to which I/O traffic from supported I/O devices are routed.
>
> "are routed" -> "are routed when "io_alloc" is enabled"?
>
Sure.
>> +
>> + CBMs are displayed in the following format:
>> +
>> + <cache_id0>=<cbm>;<cache_id1>=<cbm>;...
>> +
>> + Example::
>> +
>> + # cat /sys/fs/resctrl/info/L3/io_alloc_cbm
>> + 0=ffff;1=ffff
>> +
>> + When CDP is enabled "io_alloc_cbm" associated with the DATA and CODE
>> + resources may reflect the same values. For example, values read from and
>> + written to /sys/fs/resctrl/info/L3DATA/io_alloc_cbm may be reflected by
>> + /sys/fs/resctrl/info/L3CODE/io_alloc_cbm and vice versa.
>> +
>> Memory bandwidth(MB) subdirectory contains the following files
>> with respect to allocation:
>>
>> diff --git a/fs/resctrl/ctrlmondata.c b/fs/resctrl/ctrlmondata.c
>> index d98e0d2de09f..e78828b0408a 100644
>> --- a/fs/resctrl/ctrlmondata.c
>> +++ b/fs/resctrl/ctrlmondata.c
>> @@ -381,7 +381,8 @@ ssize_t rdtgroup_schemata_write(struct kernfs_open_file *of,
>> return ret ?: nbytes;
>> }
>>
>> -static void show_doms(struct seq_file *s, struct resctrl_schema *schema, int closid)
>> +void show_doms(struct seq_file *s, struct resctrl_schema *schema, char *resource_name,
>
> show_doms() can remain static within ctrlmondata.c by moving resctrl_io_alloc_cbm_show()
> to ctrlmondata.c
>
Yes. Moved it to ctrlmondata.c.
Thanks
Babu Moger
next prev parent reply other threads:[~2025-08-04 18:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 17:16 [PATCH v7 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Babu Moger
2025-07-10 17:16 ` [PATCH v7 01/10] x86/cpufeatures: Add support for L3 Smart Data Cache Injection Allocation Enforcement Babu Moger
2025-07-10 23:26 ` Borislav Petkov
2025-07-21 23:28 ` Reinette Chatre
2025-07-10 17:16 ` [PATCH v7 02/10] x86/resctrl: Add SDCIAE feature in the command line options Babu Moger
2025-07-21 23:29 ` Reinette Chatre
2025-07-31 16:28 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 03/10] x86,fs/resctrl: Detect io_alloc feature Babu Moger
2025-07-21 23:29 ` Reinette Chatre
2025-07-10 17:16 ` [PATCH v7 04/10] x86,fs/resctrl: Implement "io_alloc" enable/disable handlers Babu Moger
2025-07-21 23:32 ` Reinette Chatre
2025-07-31 17:40 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 05/10] fs/resctrl: Update bit_usage to reflect io_alloc Babu Moger
2025-07-21 23:35 ` Reinette Chatre
2025-08-04 21:20 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 06/10] fs/resctrl: Introduce interface to display "io_alloc" support Babu Moger
2025-07-21 23:36 ` Reinette Chatre
2025-07-31 18:51 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 07/10] fs/resctrl: Add user interface to enable/disable io_alloc feature Babu Moger
2025-07-21 23:40 ` Reinette Chatre
2025-07-31 22:52 ` Moger, Babu
2025-08-04 16:07 ` Reinette Chatre
2025-08-04 17:14 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 08/10] fs/resctrl: Introduce interface to display io_alloc CBMs Babu Moger
2025-07-21 23:42 ` Reinette Chatre
2025-08-04 18:14 ` Moger, Babu [this message]
2025-07-10 17:16 ` [PATCH v7 09/10] fs/resctrl: Modify rdt_parse_data to pass mode and CLOSID Babu Moger
2025-07-22 3:30 ` Reinette Chatre
2025-08-04 19:32 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 10/10] fs/resctrl: Introduce interface to modify io_alloc Capacity Bit Masks Babu Moger
2025-07-22 3:32 ` Reinette Chatre
2025-08-04 21:01 ` Moger, Babu
2025-07-21 23:28 ` [PATCH v7 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Reinette Chatre
2025-08-04 21:34 ` 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=4efddbf1-1e98-4ee5-8057-7b3ce5adbec2@amd.com \
--to=babu.moger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=ebiggers@google.com \
--cc=fvdl@google.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kai.huang@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=me@mixaill.net \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=perry.yuan@amd.com \
--cc=peterz@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=xin3.li@intel.com \
--cc=xin@zytor.com \
--cc=yosry.ahmed@linux.dev \
/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).