From: Reinette Chatre <reinette.chatre@intel.com>
To: Babu Moger <babu.moger@amd.com>, <tony.luck@intel.com>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>
Cc: <corbet@lwn.net>, <Dave.Martin@arm.com>, <james.morse@arm.com>,
<x86@kernel.org>, <hpa@zytor.com>, <akpm@linux-foundation.org>,
<paulmck@kernel.org>, <rdunlap@infradead.org>, <pmladek@suse.com>,
<kees@kernel.org>, <arnd@arndb.de>, <fvdl@google.com>,
<seanjc@google.com>, <pawan.kumar.gupta@linux.intel.com>,
<xin@zytor.com>, <thomas.lendacky@amd.com>,
<sohil.mehta@intel.com>, <jarkko@kernel.org>,
<chang.seok.bae@intel.com>, <ebiggers@google.com>,
<elena.reshetova@intel.com>, <ak@linux.intel.com>,
<mario.limonciello@amd.com>, <perry.yuan@amd.com>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<peternewman@google.com>, <feng.tang@linux.alibaba.com>
Subject: Re: [PATCH v11 06/10] fs/resctrl: Add user interface to enable/disable io_alloc feature
Date: Mon, 3 Nov 2025 11:05:56 -0800 [thread overview]
Message-ID: <43506b9c-5ad7-4871-8a24-11e71380321d@intel.com> (raw)
In-Reply-To: <deb3a4f19d6e138a502b136034fb88ad8b8c9c75.1761844489.git.babu.moger@amd.com>
Hi Babu,
On 10/30/25 10:15 AM, Babu Moger wrote:
...
> diff --git a/Documentation/filesystems/resctrl.rst b/Documentation/filesystems/resctrl.rst
> index 108995640ca5..89e856e6892c 100644
> --- a/Documentation/filesystems/resctrl.rst
> +++ b/Documentation/filesystems/resctrl.rst
> @@ -152,6 +152,29 @@ related to allocation:
> "not supported":
> Support not available for this resource.
>
> + The feature can be modified by writing to the interface, for example:
> +
> + To enable:
> + # echo 1 > /sys/fs/resctrl/info/L3/io_alloc
> +
> + To disable:
> + # echo 0 > /sys/fs/resctrl/info/L3/io_alloc
> +
Above examples are missing the '::' that will format them as fixed width text blocks
used for these shell examples.
> + 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 (CDP_CODE), making this CLOSID no longer
> + available for general (CPU) cache allocation for both the CDP_CODE
> + and CDP_DATA resources.
> +
> Memory bandwidth(MB) subdirectory contains the following files
> with respect to allocation:
>
With the doc formatting fixed:
| Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
next prev parent reply other threads:[~2025-11-03 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 17:15 [PATCH v11 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Babu Moger
2025-10-30 17:15 ` [PATCH v11 01/10] x86/cpufeatures: Add support for L3 Smart Data Cache Injection Allocation Enforcement Babu Moger
2025-10-30 17:15 ` [PATCH v11 02/10] x86/resctrl: Add SDCIAE feature in the command line options Babu Moger
2025-10-30 17:15 ` [PATCH v11 03/10] x86,fs/resctrl: Detect io_alloc feature Babu Moger
2025-10-30 17:15 ` [PATCH v11 04/10] x86,fs/resctrl: Implement "io_alloc" enable/disable handlers Babu Moger
2025-10-30 17:15 ` [PATCH v11 05/10] fs/resctrl: Introduce interface to display "io_alloc" support Babu Moger
2025-10-30 17:15 ` [PATCH v11 06/10] fs/resctrl: Add user interface to enable/disable io_alloc feature Babu Moger
2025-11-03 19:05 ` Reinette Chatre [this message]
2025-11-03 21:36 ` Babu Moger
2025-11-05 16:46 ` Dave Martin
2025-11-05 17:31 ` Moger, Babu
2025-11-05 18:25 ` Luck, Tony
2025-11-06 0:48 ` Reinette Chatre
2025-10-30 17:15 ` [PATCH v11 07/10] fs/resctrl: Introduce interface to display io_alloc CBMs Babu Moger
2025-10-30 17:15 ` [PATCH v11 08/10] fs/resctrl: Modify struct rdt_parse_data to pass mode and CLOSID Babu Moger
2025-10-30 17:15 ` [PATCH v11 09/10] fs/resctrl: Introduce interface to modify io_alloc capacity bitmasks Babu Moger
2025-10-30 17:15 ` [PATCH v11 10/10] fs/resctrl: Update bit_usage to reflect io_alloc Babu Moger
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=43506b9c-5ad7-4871-8a24-11e71380321d@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=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=elena.reshetova@intel.com \
--cc=feng.tang@linux.alibaba.com \
--cc=fvdl@google.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=jarkko@kernel.org \
--cc=kees@kernel.org \
--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=pawan.kumar.gupta@linux.intel.com \
--cc=perry.yuan@amd.com \
--cc=peternewman@google.com \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®