RE: [EXT] Re: resctrl2 - status

[Amit Singh Tomar]

-----Original Message-----
From: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx> 
Sent: Tuesday, August 29, 2023 3:53 PM
To: Reinette Chatre <reinette.chatre@xxxxxxxxx>
Cc: Luck, Tony <tony.luck@xxxxxxxxx>; Amit Singh Tomar <amitsinght@xxxxxxxxxxx>; Yu, Fenghua <fenghua.yu@xxxxxxxxx>; james.morse@xxxxxxx; George Cherian <gcherian@xxxxxxxxxxx>; robh@xxxxxxxxxx; peternewman@xxxxxxxxxx; Drew Fustini <dfustini@xxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
Subject: [EXT] Re: resctrl2 - status

External Email

----------------------------------------------------------------------
On Fri, 25 Aug 2023 13:20:22 -0700
Reinette Chatre <reinette.chatre@xxxxxxxxx> wrote:

> Hi Tony,
> 
> On 8/25/2023 12:44 PM, Luck, Tony wrote:
> >>>> Alternatively, can user space just take a "load all resctrl 
> >>>> modules and see what sticks" (even modules of different 
> >>>> architectures since a user space may want to be generic) approach?
> >>>
> >>> This mostly works. Except for the cases where different modules 
> >>> access the same underlying hardware, so can't be loaded together.
> >>>
> >>> Examples:
> >>>
> >>> rdt_l3_cat vs. rdt_l3_cdp - user needs to decide whether they want CDP or not.
> >>> But this is already true ... they have to decide whether to pass 
> >>> the "-o cdp" option to mount.
> >>>
> >>> rdt_l3_mba vs. rdt_l3_mba_MBps - does the user want to control 
> >>> memory bandwidth with percentages, or with MB/sec values. Again 
> >>> the user already has to make this decision when choosing mount options.
> >>>
> >>>
> >>> Maybe the "What resctrl options does this machine support?" 
> >>> question would be best answered with a small utility?
> >>
> >> A user space utility or a kernel provided utility? If it is a user 
> >> space utility I think it would end up needing to duplicate what the 
> >> kernel is required to do to know if a particular feature is 
> >> supported. It seems appropriate that this could be a kernel utility 
> >> that can share this existing information with user space. resctrl already supports the interface for this via /sys/fs/resctrl/info.
> > 
> > I was imagining a user space utility. Even though /proc/cpuinfo 
> > doesn't show all features, a utility has access to all the CPUID 
> > leaves that contain the details of each feature enumeration.
> 
> For x86 that may work (in some scenarios, see later) for now but as I 
> understand Arm would need a different solution where I believe the 
> information is obtained via ACPI. I think it is unnecessary to require 
> user space to have parsers for CPUID and ACPI if that same information 
> needs to be parsed by the kernel and there already exists an interface 
> with which the information is communicated from kernel to user space. 
> Also, just because information CPUID shows a feature is supported by 
> the hardware does not mean that the kernel has support for that 
> feature. This could be because of a feature mismatch between user 
> space and kernel, or even some features disabled for use via the, for example "rdt=!l3cat", kernel parameter.

James probably also has views on this, but I wouldn't expect userspace to go anywhere near ACPI parsing. If the description of what MPAM features are supported (before resctrl is running) is necessary, then we should add it to the existing description of the various caches etc.  Maybe somewhere in /sys/bus/node/devices/nodeX/cpuY/cache/indexZ/
for the caches
and
/sys/bus/node/devices/nodeX for the DRAM controllers.
[>>] Or may be all the MPAM features list is unified at one place, something like this ?
https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git/commit/?h=mpam/snapshot/v6.5-rc1&id=c32874cd1d68241c481a9d0c32c8c65d019c247e

I'm sure we can find somewhere sensible for other things covered by MPAM.
The MPAM table parsers and some early code to query features from the hardware should be able to figure out what is needed.

Perhaps x86 systems could provide similar descriptions but originating from CPUID etc.

Jonathan

> 
> >> fyi ... as with previous attempts to discuss this work I find it 
> >> difficult to discuss this work when you are selective about what 
> >> you want to discuss/answer and just wipe the rest. Through this I 
> >> understand that I am not your target audience.
> > 
> > Not my intent. I value your input highly. I'm maybe too avid a 
> > follower of the "trim your replies" school of e-mail etiquette. I 
> > thought I'd covered the gist of your message.
> > 
> > I'll try to be more thorough in responding in the future.  
> 
> Two items from my previous email remain open:
> 
> First, why does making the code modular require everything to be 
> loadable modules?
> I think that it is great that the code is modular. Ideally it will 
> help to support the other architectures. As you explain this modular 
> design also has the benefit that "modules" can be loaded and unloaded after resctrl mount.
> Considering your example of MBA and MBA_MBps support ... if I 
> understand correctly with code being modular it enables changes from 
> one to the other after resctrl mount. User can start with MBA and then 
> switch to MBA_MBps without needing to unmount resctrl. What I do not 
> understand is why does the code being modular require everything to be 
> modules? Why, for example, could a user not interact with a resctrl 
> file that enables the user to make this switch from, for example, MBA 
> to MBA_MBps? With this the existing interfaces can remain to be 
> respected, the existing mount parameters need to remain anyway, while enabling future "more modular" usages.
> 
> Second, copied from my previous email, what is the plan to deal with 
> current users that just mount resctrl and expect to learn from it what 
> features are supported?
> 
> Reinette
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.or
> g_mailman_listinfo_linux-2Darm-2Dkernel&d=DwICAg&c=nKjWec2b6R0mOyPaz7x
> tfQ&r=V_GK7jRuCHDErm6txmgDK1-MbUihtnSQ3gPgB-A-JKU&m=ri5Ay9ia3NmwAS6P94yjZ7rPIR1dIqrIAIjpslfwcd5ulIIs5BNEG9jmTlq6H6o8&s=KZMxmC8InOxAyxgrDig96R2aKf2hc1C_hk_1413pjCI&e=
>