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 10/10] fs/resctrl: Update bit_usage to reflect io_alloc
Date: Wed, 17 Sep 2025 23:08:53 -0700 [thread overview]
Message-ID: <79b2d040-a3e6-40db-b545-bb07d42c8c29@intel.com> (raw)
In-Reply-To: <549a772b83461fb4cb7b6e8dabc60724cbe96ad0.1756851697.git.babu.moger@amd.com>
Hi Babu,
On 9/2/25 3:41 PM, Babu Moger wrote:
> When the io_alloc feature is enabled, a portion of the cache can be
> configured for shared use between hardware and software.
(repetitive)
>
> Update bit_usage representation to reflect the io_alloc configuration.
> Revise the documentation for "shareable_bits" and "bit_usage" to reflect
> the impact of io_alloc feature.
Attempt at new version, please feel free to improve:
The "shareable_bits" and "bit_usage" resctrl files associated with cache
resources give insight into how instances of a cache is used.
Update the annotated capacity bitmasks displayed by "bit_usage" to include the
cache portions allocated for I/O via the "io_alloc" feature. "shareable_bits" is
a global bitmask of shareable cache with I/O and can thus not present the
per-domain I/O allocations possible with the "io_alloc" feature. Revise the
"shareable_bits" documentation to direct users to "bit_usage" for accurate
cache usage information.
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
...
> ---
> Documentation/filesystems/resctrl.rst | 35 ++++++++++++++++-----------
> fs/resctrl/ctrlmondata.c | 2 +-
> fs/resctrl/internal.h | 2 ++
> fs/resctrl/rdtgroup.c | 21 ++++++++++++++--
> 4 files changed, 43 insertions(+), 17 deletions(-)
>
> diff --git a/Documentation/filesystems/resctrl.rst b/Documentation/filesystems/resctrl.rst
> index 7e3eda324de5..72ea6f3f36bc 100644
> --- a/Documentation/filesystems/resctrl.rst
> +++ b/Documentation/filesystems/resctrl.rst
> @@ -90,12 +90,19 @@ related to allocation:
> must be set when writing a mask.
>
> "shareable_bits":
> - Bitmask of shareable resource with other executing
> - entities (e.g. I/O). User can use this when
> - setting up exclusive cache partitions. Note that
> - some platforms support devices that have their
> - own settings for cache use which can over-ride
> - these bits.
> + Bitmask of shareable resource with other executing entities
> + (e.g. I/O). Applies to all instances of this resource. User
> + can use this when setting up exclusive cache partitions.
> + Note that some platforms support devices that have their
> + own settings for cache use which can over-ride these bits.
> +
> + When "io_alloc" is enabled, a portion of each cache instance can
> + be configured for shared use between hardware and software.
> + "bit_usage" should be used to see which portions of each cache
> + instance is configured for hardware use via "io_alloc" feature
> + because every cache instance can have its "io_alloc" bitmask
> + configured independently via io_alloc_cbm.
io_alloc_cbm -> "io_alloc_cbm" (to consistently place names of resctrl files in quotes)
> +
> "bit_usage":
> Annotated capacity bitmasks showing how all
> instances of the resource are used. The legend is:
> @@ -109,16 +116,16 @@ related to allocation:
> "H":
> Corresponding region is used by hardware only
> but available for software use. If a resource
> - has bits set in "shareable_bits" but not all
> - of these bits appear in the resource groups'
> - schematas then the bits appearing in
> - "shareable_bits" but no resource group will
> - be marked as "H".
> + has bits set in "shareable_bits" or "io_alloc_cbm"
> + but not all of these bits appear in the resource
> + groups' schematas then the bits appearing in
I understand that you are just copying this but "schemata" is plural of "schema". Since you
are copying this text, could you please fix "schematas" to be "schemata" while doing so?
> + "shareable_bits" or "io_alloc_cbm" but no
> + resource group will be marked as "H".
> "X":
> Corresponding region is available for sharing and
> - used by hardware and software. These are the
> - bits that appear in "shareable_bits" as
> - well as a resource group's allocation.
> + used by hardware and software. These are the bits
> + that appear in "shareable_bits" or "io_alloc_cbm"
> + as well as a resource group's allocation.
> "S":
> Corresponding region is used by software
> and available for sharing.
Reinette
next prev parent reply other threads:[~2025-09-18 6:09 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
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 [this message]
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=79b2d040-a3e6-40db-b545-bb07d42c8c29@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.