From: Reinette Chatre <reinette.chatre@intel.com>
To: Babu Moger <babu.moger@amd.com>, <corbet@lwn.net>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>
Cc: <fenghua.yu@intel.com>, <dave.hansen@linux.intel.com>,
<x86@kernel.org>, <hpa@zytor.com>, <paulmck@kernel.org>,
<akpm@linux-foundation.org>, <quic_neeraju@quicinc.com>,
<rdunlap@infradead.org>, <damien.lemoal@opensource.wdc.com>,
<songmuchun@bytedance.com>, <peterz@infradead.org>,
<jpoimboe@kernel.org>, <pbonzini@redhat.com>,
<chang.seok.bae@intel.com>, <pawan.kumar.gupta@linux.intel.com>,
<jmattson@google.com>, <daniel.sneddon@linux.intel.com>,
<sandipan.das@amd.com>, <tony.luck@intel.com>,
<james.morse@arm.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <bagasdotme@gmail.com>,
<eranian@google.com>, <christophe.leroy@csgroup.eu>,
<jarkko@kernel.org>, <adrian.hunter@intel.com>,
<quic_jiles@quicinc.com>, <peternewman@google.com>
Subject: Re: [PATCH v13 04/10] x86/resctrl: Add comments on RFTYPE flags hierarchy
Date: Fri, 13 Oct 2023 14:23:56 -0700 [thread overview]
Message-ID: <d4a33013-0448-4c36-a168-b3a953024962@intel.com> (raw)
In-Reply-To: <20231013202602.2492645-5-babu.moger@amd.com>
Hi Babu,
On 10/13/2023 1:25 PM, Babu Moger wrote:
> resctrl uses RFTYPE flags for creating resctrl directory structure.
>
> Definitions and directory structures are not documented. Add
> comments to improve the readability and help future additions.
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
> v13: Fixed the format issues in the documentation. Needed few minor format
> changes to address the syntax issues.(Reinette)
> Removed "Reviewed-by and Tested-by" flags as the patch has changed.
>
> v12: Moved the comments from arch/x86/kernel/cpu/resctrl/internal.h
> to Documentation/arch/x86/resctrl.rst. (Boris)
> ---
> Documentation/arch/x86/resctrl.rst | 64 ++++++++++++++++++++++++++++++
> 1 file changed, 64 insertions(+)
>
> diff --git a/Documentation/arch/x86/resctrl.rst b/Documentation/arch/x86/resctrl.rst
> index 178ab1d8f747..1163da74f734 100644
> --- a/Documentation/arch/x86/resctrl.rst
> +++ b/Documentation/arch/x86/resctrl.rst
> @@ -369,6 +369,70 @@ When monitoring is enabled all MON groups will also contain:
> the sum for all tasks in the CTRL_MON group and all tasks in
> MON groups. Please see example section for more details on usage.
>
> +RESCTRL filesystem implementation notes
> +=======================================
> +RESCTRL filesystem has two main components
> + a. info
> + b. base
> +
> + /sys/fs/resctrl/
> + |
> + -> info
> + |
> + | (Top level directory named "info". Contains files that
> + | provide details on control and monitoring resources")
> + |
> + -> base
> +
Could you please do a "make htmldocs" and then ensure that the output looks sane?
The resulting output does not look right to me. For example, the above turns into
a single line that looks like:
/sys/fs/resctrl/ | -> info | | (Top level directory named "info". Contains files that | provide details on control and monitoring resources") | -> base
The spacing also looks off when viewing this in html.
> + (Root directory associated with default resource group as
> + well as directories created by user for MON and CTRL groups.
> + Contains files to interact with MON and CTRL groups)
> +
> + Note: resctrl uses flags for files, not for directories.
> + Directories are created based on the resource type. Added
> + directories below for better understanding. The RFTYPE flags
> + are defined in arch/x86/kernel/cpu/resctrl/internal.h.
> +
> + info directory structure
> +
You removed the separator in order to pass the syntax issue but now there is
no indication that this is a heading and the content becomes harder to understand.
> + -> RFTYPE_INFO
> + Directory: info
> +
> + -> RFTYPE_TOP (Files in top level of info directory)
> + File: last_cmd_status
> +
> + -> RFTYPE_MON (Files for all monitoring resources)
> + Directory: L3_MON
> + Files: mon_features, num_rmids
> +
> + -> RFTYPE_RES_CACHE (Files for cache monitoring resources)
> + Directory: L3_MON
> + Files: max_threshold_occupancy,
> + mbm_total_bytes_config,
> + mbm_local_bytes_config
> +
> + -> RFTYPE_CTRL (Files for all control resources)
> + Directories: L2, L3, MB, SMBA, L2CODE, L2DATA, L3CODE, L3DATA
> + File: num_closids
> +
> + -> RFTYPE_RES_CACHE (Files for cache control resources)
> + Directories: L2, L3, L2CODE, L2DATA, L3CODE, L3DATA
> + Files: bit_usage, cbm_mask, min_cbm_bits,
> + shareable_bits
> +
> + -> RFTYPE_RES_MB (Files for memory control resources)
> + Directories: MB, SMBA
> + Files: bandwidth_gran, delay_linear,
> + min_bandwidth, thread_throttle_mode
> +
> + base directory structure
> +
Same here.
> + -> RFTYPE_BASE (Files common for both MON and CTRL groups)
> + Files: cpus, cpus_list, tasks
> +
> + -> RFTYPE_CTRL (Files for CTRL group)
> + Files: mode, schemata, size
> +
> Resource allocation rules
> -------------------------
>
Reinette
next prev parent reply other threads:[~2023-10-13 21:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 20:25 [PATCH v13 00/10] x86/resctrl: Miscellaneous resctrl features Babu Moger
2023-10-13 20:25 ` [PATCH v13 01/10] x86/resctrl: Add multiple tasks to the resctrl group at once Babu Moger
2023-10-13 20:25 ` [PATCH v13 02/10] x86/resctrl: Simplify rftype flag definitions Babu Moger
2023-10-13 20:25 ` [PATCH v13 03/10] x86/resctrl: Rename rftype flags for consistency Babu Moger
2023-10-13 20:25 ` [PATCH v13 04/10] x86/resctrl: Add comments on RFTYPE flags hierarchy Babu Moger
2023-10-13 21:23 ` Reinette Chatre [this message]
2023-10-13 21:39 ` Moger, Babu
2023-10-14 23:06 ` Moger, Babu
2023-10-16 20:46 ` Reinette Chatre
2023-10-16 21:10 ` Borislav Petkov
2023-10-16 21:58 ` Moger, Babu
2023-10-17 17:47 ` Moger, Babu
2023-10-17 20:11 ` Reinette Chatre
2023-10-13 20:25 ` [PATCH v13 05/10] x86/resctrl: Unwind the errors inside rdt_enable_ctx() Babu Moger
2023-10-13 20:25 ` [PATCH v13 06/10] x86/resctrl: Move default group file creation to mount Babu Moger
2023-10-13 20:25 ` [PATCH v13 07/10] x86/resctrl: Introduce "-o debug" mount option Babu Moger
2023-10-13 20:26 ` [PATCH v13 08/10] x86/resctrl: Display CLOSID for resource group Babu Moger
2023-10-13 20:26 ` [PATCH v13 09/10] x86/resctrl: Add support for the files for MON groups only Babu Moger
2023-10-13 20:26 ` [PATCH v13 10/10] x86/resctrl: Display RMID of resource group Babu Moger
2023-10-13 21:24 ` Reinette Chatre
2023-10-13 21:40 ` 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=d4a33013-0448-4c36-a168-b3a953024962@intel.com \
--to=reinette.chatre@intel.com \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=babu.moger@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=jarkko@kernel.org \
--cc=jmattson@google.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peternewman@google.com \
--cc=peterz@infradead.org \
--cc=quic_jiles@quicinc.com \
--cc=quic_neeraju@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=sandipan.das@amd.com \
--cc=songmuchun@bytedance.com \
--cc=tglx@linutronix.de \
--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®