Hi Tony, On 10/9/24 17:49, Tony Luck wrote: > On Wed, Oct 09, 2024 at 12:39:33PM -0500, Babu Moger wrote: >> +"num_mbm_cntrs": >> + The number of monitoring counters available for assignment when the >> + architecture supports mbm_cntr_assign mode. > > It's not obvious (to me) how these counters work. When I create > a group with both local and total monitoring enabled, does that > use up two counters (even though I only used up one RMID)? That is correct. One RMID can be associated with multiple h/w counters. > > Are the counters multi-purpose. E.g. if I disable local counting > on all groups, are the freed-up counters available for use to > count total bandwidth on some additional groups? Yes. That is correct. With 32 counters you can enable both the events on up to 16 groups. You can also enable only one event in up to 32 groups. > >>From the examples it looks like if there are free counters > available when user does mkdir, then they will be assigned > to the new rdtgroup. If only one counter is free, does it > get assigned to local or total? Right now total event takes a priority. All good points. How about this text: "num_mbm_cntrs": The number of monitoring counters available for assignment when the architecture supports mbm_cntr_assign mode. Resctrl subsystem provides the interface to count maximum of two memory bandwidth events per group, from a combination of available total and local events. Keeping the current interface, users can enable a maximum of 2 counters per group. User will also have the option to enable only one counter to the group to maximize the number of groups monitored. -- Thanks Babu Moger
