Documentation/x86/resctrl_ui.rst

53 only those files and directories supported by the system will be created.
104 			      "shareable_bits" but no resource group will
153 If RDT monitoring is available there will be an "L3_MON" directory
173 control files). If the command was successful, it will read as "ok".
174 If the command failed, it will provide more information that can be
202 Removing a directory will move all tasks and cpus owned by the group it
204 will automatically remove all MON groups below it.
210 	this group. Writing a task id to the file will add a task to the
220 	this group. Writing a mask to this file will add and remove
224 	When the resource group is in pseudo-locked mode this file will
233 When control is enabled all CTRL_MON groups will also contain:
251 	file. On successful pseudo-locked region creation the mode will
254 When monitoring is enabled all MON groups will also contain:
258 	RDT event. E.g. on a system with two L3 domains there will
285    then RDT events for the task will be reported in that group.
289    for the task will be reported in that group.
291 3) Otherwise RDT events for the task will be reported in the root level
301 groups you will likely see that the old group is still showing 3 MB and
304 you will likely see the occupancy in the old group go down as cache lines
310 with a smaller cache partition will not evict any cache lines. The
346 a resource we use a "Cache ID". At a given cache level this will be a
397 << 100%. Hence increasing the bandwidth percentage will not yield any
469 Reading the schemata file will show the state of all resources
489 fill, and from that point on will only serve cache hits. The cache
499   from the user of the cache region that will contain the pseudo-locked
511   any CAT allocation. Even though the cache pseudo-locked region will from
513   any CLOS will be able to access the memory in the pseudo-locked region since
518 Cache pseudo-locking increases the probability that data will remain
523 power off cache. Deeper C-states will automatically be restricted on
529 within the code will not allow an application to map pseudo-locked memory
555 On successful pseudo-locked region creation the "mode" file will contain
557 group will exist in /dev/pseudo_lock. This character device can be mmap()'ed
589      writing "1" to the pseudo_lock_measure file will trigger the latency
593      writing "2" to the pseudo_lock_measure file will trigger the L2 cache
597      writing "3" to the pseudo_lock_measure file will trigger the L3 cache
732 on socket 0. Most uses of resource groups will also constrain which
802 In this example a new exclusive resource group will be created on a L2 CAT
804 capacity bitmask. The new exclusive resource group will be configured to use
817 We could attempt to create the new resource group at this point, but it will
842 A new resource group will on creation not overlap with an exclusive resource
852 The bit_usage will reflect how the cache is used::
884 Create a new resource group that will be associated with the pseudo-locked
885 region, indicate that it will be used for a pseudo-locked region, and
892 On success the resource group's mode will change to pseudo-locked, the
893 bit_usage will reflect the pseudo-locked region, and the character device
894 exposing the pseudo-locked region will exist::
1161 the resctrl will still mount but cannot create CTRL_MON directories.