From: Reinette Chatre <reinette.chatre@intel.com>
To: Babu Moger <babu.moger@amd.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>, <kas@kernel.org>,
<rick.p.edgecombe@intel.com>, <akpm@linux-foundation.org>,
<paulmck@kernel.org>, <pmladek@suse.com>,
<pawan.kumar.gupta@linux.intel.com>, <rostedt@goodmis.org>,
<kees@kernel.org>, <arnd@arndb.de>, <fvdl@google.com>,
<seanjc@google.com>, <thomas.lendacky@amd.com>,
<manali.shukla@amd.com>, <perry.yuan@amd.com>,
<sohil.mehta@intel.com>, <xin@zytor.com>, <peterz@infradead.org>,
<mario.limonciello@amd.com>, <gautham.shenoy@amd.com>,
<nikunj@amd.com>, <dapeng1.mi@linux.intel.com>,
<ak@linux.intel.com>, <chang.seok.bae@intel.com>,
<ebiggers@google.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-coco@lists.linux.dev>,
<kvm@vger.kernel.org>
Subject: Re: [PATCH v9 05/10] fs/resctrl: Introduce interface to display "io_alloc" support
Date: Wed, 17 Sep 2025 22:28:00 -0700 [thread overview]
Message-ID: <7b1452b2-38d7-49e1-bd34-ea61eca01419@intel.com> (raw)
In-Reply-To: <5f368e4f65629c5bf377466e9004733b625c5807.1756851697.git.babu.moger@amd.com>
Hi Babu,
On 9/2/25 3:41 PM, Babu Moger wrote:
> "io_alloc" feature in resctrl allows direct insertion of data from I/O
> devices into the cache.
>
> Introduce the 'io_alloc' resctrl file to indicate the support for the
> feature.
Changelog that aims to address feeback received in ABMC series (avoid repetition
and document any non-obvious things), please feel free to improve:
Introduce the "io_alloc" resctrl file to the "info" area of a cache
resource, for example /sys/fs/resctrl/info/L3/io_alloc. "io_alloc"
indicates support for the "io_alloc" feature that allows direct
insertion of data from I/O devices into the cache.
Restrict exposing support for "io_alloc" to the L3 resource that is the
only resource where this feature can be backed by AMD's L3 Smart Data Cache
Injection Allocation Enforcement (SDCIAE). With that, the "io_alloc" file is only
visible to user space if the L3 resource supports "io_alloc". Doing
so makes the file visible for all cache resources though, for example also L2
cache (if it supports cache allocation). As a consequence, add capability for
file to report expected "enabled" and "disabled", as well as "not supported".
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
...
> ---
> Documentation/filesystems/resctrl.rst | 30 +++++++++++++++++++++++++++
> fs/resctrl/ctrlmondata.c | 21 +++++++++++++++++++
> fs/resctrl/internal.h | 5 +++++
> fs/resctrl/rdtgroup.c | 24 ++++++++++++++++++++-
> 4 files changed, 79 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/resctrl.rst b/Documentation/filesystems/resctrl.rst
> index 4866a8a4189f..89aab17b00cb 100644
> --- a/Documentation/filesystems/resctrl.rst
> +++ b/Documentation/filesystems/resctrl.rst
> @@ -136,6 +136,36 @@ related to allocation:
> "1":
> Non-contiguous 1s value in CBM is supported.
>
> +"io_alloc":
> + "io_alloc" enables system software to configure the portion of
> + the cache allocated for I/O traffic. File may only exist if the
> + system supports this feature on some of its cache resources.
> +
> + "disabled":
> + Resource supports "io_alloc" but the feature is disabled.
> + Portions of cache used for allocation of I/O traffic cannot
> + be configured.
> + "enabled":
> + Portions of cache used for allocation of I/O traffic
> + can be configured using "io_alloc_cbm".
> + "not supported":
> + Support not available for this resource.
> +
After trying to rework the changelogs I believe the portion of doc below is better suited for
the next patch that adds support for enable/disable where CLOSIDs are relevant.
> + The underlying implementation may reduce resources available to
> + general (CPU) cache allocation. See architecture specific notes
> + below. Depending on usage requirements the feature can be enabled
> + or disabled.
> +
> + On AMD systems, io_alloc feature is supported by the L3 Smart
> + Data Cache Injection Allocation Enforcement (SDCIAE). The CLOSID for
> + io_alloc is the highest CLOSID supported by the resource. When
> + io_alloc is enabled, the highest CLOSID is dedicated to io_alloc and
> + no longer available for general (CPU) cache allocation. When CDP is
> + enabled, io_alloc routes I/O traffic using the highest CLOSID allocated
> + for the instruction cache (L3CODE), making this CLOSID no longer
> + available for general (CPU) cache allocation for both the L3CODE and
> + L3DATA resources.
> +
> Memory bandwidth(MB) subdirectory contains the following files
> with respect to allocation:
>
Reinette
next prev parent reply other threads:[~2025-09-18 5:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 22:41 [PATCH v9 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Babu Moger
2025-09-02 22:41 ` [PATCH v9 01/10] x86/cpufeatures: Add support for L3 Smart Data Cache Injection Allocation Enforcement Babu Moger
2025-09-18 5:08 ` Reinette Chatre
2025-09-19 15:45 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 02/10] x86/resctrl: Add SDCIAE feature in the command line options Babu Moger
2025-09-18 5:09 ` Reinette Chatre
2025-09-19 16:40 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 03/10] x86,fs/resctrl: Detect io_alloc feature Babu Moger
2025-09-18 5:15 ` Reinette Chatre
2025-09-19 16:53 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 04/10] x86,fs/resctrl: Implement "io_alloc" enable/disable handlers Babu Moger
2025-09-18 5:19 ` Reinette Chatre
2025-09-19 17:18 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 05/10] fs/resctrl: Introduce interface to display "io_alloc" support Babu Moger
2025-09-18 5:28 ` Reinette Chatre [this message]
2025-09-19 17:49 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 06/10] fs/resctrl: Add user interface to enable/disable io_alloc feature Babu Moger
2025-09-18 5:37 ` Reinette Chatre
2025-09-19 19:09 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 07/10] fs/resctrl: Introduce interface to display io_alloc CBMs Babu Moger
2025-09-18 5:43 ` Reinette Chatre
2025-09-19 19:38 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 08/10] fs/resctrl: Modify rdt_parse_data to pass mode and CLOSID Babu Moger
2025-09-18 5:44 ` Reinette Chatre
2025-09-19 19:49 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 09/10] fs/resctrl: Introduce interface to modify io_alloc Capacity Bit Masks Babu Moger
2025-09-18 6:03 ` Reinette Chatre
2025-09-19 20:49 ` Moger, Babu
2025-09-22 22:48 ` Reinette Chatre
2025-09-25 18:54 ` Moger, Babu
2025-09-02 22:41 ` [PATCH v9 10/10] fs/resctrl: Update bit_usage to reflect io_alloc Babu Moger
2025-09-18 6:08 ` Reinette Chatre
2025-09-19 21:05 ` 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=7b1452b2-38d7-49e1-bd34-ea61eca01419@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=corbet@lwn.net \
--cc=dapeng1.mi@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=fvdl@google.com \
--cc=gautham.shenoy@amd.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kas@kernel.org \
--cc=kees@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manali.shukla@amd.com \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=perry.yuan@amd.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rick.p.edgecombe@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=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