From: Reinette Chatre <reinette.chatre@intel.com>
To: Ben Horgan <ben.horgan@arm.com>, <linux-kernel@vger.kernel.org>
Cc: <tony.luck@intel.com>, <Dave.Martin@arm.com>,
<james.morse@arm.com>, <babu.moger@amd.com>, <tglx@kernel.org>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<x86@kernel.org>, <hpa@zytor.com>, <fenghuay@nvidia.com>,
<tan.shaopeng@fujitsu.com>
Subject: Re: [PATCH v4 6/7] fs/resctrl: Document that automatic counter assignment is best effort
Date: Fri, 27 Mar 2026 09:24:35 -0700 [thread overview]
Message-ID: <8d51eef4-c52c-454c-b1fc-89549e544a13@intel.com> (raw)
In-Reply-To: <20260326172551.1553871-7-ben.horgan@arm.com>
Hi Ben,
On 3/26/26 10:25 AM, Ben Horgan wrote:
> When using automatic counter assignment it's useful for a user to know
> which counters they can expect to be assigned on group creation.
>
> Document that automatic counter assignment is best effort and how to
> discover any assignment failures.
>
> Suggested-by: Reinette Chatre <reinette.chatre@intel.com>
> Signed-off-by: Ben Horgan <ben.horgan@arm.com>
> ---
>
> Hi Reinette,
> I've just taken your suggested paragraph with a minor tweak (s/scenario/a
> scenario/) and moved it above the examples as I think it makes sense to
> keep examples last in each section.
> ---
> Documentation/filesystems/resctrl.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/filesystems/resctrl.rst b/Documentation/filesystems/resctrl.rst
> index ba609f8d4de5..68cada238844 100644
> --- a/Documentation/filesystems/resctrl.rst
> +++ b/Documentation/filesystems/resctrl.rst
> @@ -472,6 +472,12 @@ with the following files:
> "1":
> Auto assignment is enabled.
>
> + Automatic counter assignment is done with best effort. If auto
> + assignment is enabled but there are not enough available counters then
> + monitor group creation could succeed while one or more events belonging
> + to the group may not have a counter assigned. Consult last_cmd_status
"not have a counter assigned" -> "not have a counter assigned in all domains"?
> + for details during such a scenario.
While last_cmd_status would indicate a failure it is best for user space to
consult mbm_L3_assignments for the accurate counter assignment state ("the
details"). It is starting to sound like the documentation is directing user space
to last_cmd_status for state and I would like to avoid this. How about replacing
"Consult last_cmd_status ..." sentence with "Consult mbm_L3_assignments for
counter assignment states of the new group."?
> +
> Example::
>
> # echo 0 > /sys/fs/resctrl/info/L3_MON/mbm_assign_on_mkdir
Reinette
next prev parent reply other threads:[~2026-03-27 16:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 17:25 [PATCH v4 0/7] x86,fs/resctrl: Pave the way for MPAM counter assignment Ben Horgan
2026-03-26 17:25 ` [PATCH v4 1/7] fs/resctrl: Tidy up the error path in resctrl_mkdir_event_configs() Ben Horgan
2026-03-27 16:06 ` Reinette Chatre
2026-03-26 17:25 ` [PATCH v4 2/7] x86,fs/resctrl: Make 'event_filter' files read only if they're not configurable Ben Horgan
2026-03-27 16:13 ` Reinette Chatre
2026-03-27 17:15 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 3/7] fs/resctrl: Disallow the software controller when MBM counters are assignable Ben Horgan
2026-03-27 16:14 ` Reinette Chatre
2026-03-27 17:24 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 4/7] x86,fs/resctrl: Add monitor property 'mbm_cntr_assign_fixed' Ben Horgan
2026-03-27 16:15 ` Reinette Chatre
2026-03-26 17:25 ` [PATCH v4 5/7] fs/resctrl: Continue counter allocation after failure Ben Horgan
2026-03-27 16:21 ` Reinette Chatre
2026-04-14 14:42 ` Ben Horgan
2026-04-15 14:27 ` Reinette Chatre
2026-04-15 14:46 ` Ben Horgan
2026-04-15 15:38 ` Reinette Chatre
2026-04-15 16:31 ` Ben Horgan
2026-04-15 17:28 ` Reinette Chatre
2026-04-16 8:32 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 6/7] fs/resctrl: Document that automatic counter assignment is best effort Ben Horgan
2026-03-27 16:24 ` Reinette Chatre [this message]
2026-04-14 14:55 ` Ben Horgan
2026-03-26 17:25 ` [PATCH v4 7/7] fs/resctrl: Document tasks file behaviour for task id 0 and idle tasks Ben Horgan
2026-03-27 16:40 ` Reinette Chatre
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=8d51eef4-c52c-454c-b1fc-89549e544a13@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tan.shaopeng@fujitsu.com \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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®