Lines Matching full:resource
5 User Interface for Resource Control feature
14 Intel refers to this feature as Intel Resource Director Technology(Intel(R) RDT).
21 RDT (Resource Director Technology) Allocation "rdt_a"
55 and allocation, see the "Resource alloc and monitor groups" section.
61 resources. Each resource has its own subdirectory. The subdirectory
62 names reflect the resource names.
67 Cache resource(L3/L2) subdirectory contains the following files
72 resource. The kernel uses the smallest number of
75 The bitmask which is valid for this resource.
82 Bitmask of shareable resource with other executing
90 instances of the resource are used. The legend is:
100 but available for software use. If a resource
102 of these bits appear in the resource groups'
104 "shareable_bits" but no resource group will
110 well as a resource group's allocation.
116 one resource group. No sharing allowed.
151 monitoring is enabled for the resource.
171 Resource alloc and monitor groups
174 Resource groups are represented as directories in the resctrl file
181 resource (see "schemata" below). The root and these additional top level
212 When the resource group is in pseudo-locked mode this file will
225 Each resource has its own line and format - see below for details.
233 The "mode" of the resource group dictates the sharing of its
234 allocations. A "shareable" resource group allows sharing of its
235 allocations while an "exclusive" resource group does not. A
238 pseudo-locked region's schemata to the resource group's "schemata"
255 Resource allocation rules
270 Resource monitoring rules
301 Hardware uses CLOSid(Class of service ID) and an RMID(Resource monitoring ID)
303 the resource groups are mapped to these IDs based on the kind of group. The
323 Each line in the file describes one resource. The line starts with
324 the name of the resource, followed by specific values to be applied
325 in each of the instances of that resource on the system.
334 a resource we use a "Cache ID". At a given cache level this will be a
345 the resctrl file system in "info/{resource}/cbm_mask". Intel hardware
355 For Memory bandwidth resource, by default the user controls the resource
534 1) Create a new resource group by creating a new directory in /sys/fs/resctrl.
535 2) Change the new resource group's mode to "pseudo-locksetup" by writing
542 "pseudo-locked" and a new character device with the same name as the resource
665 The default resource group is unmodified, so we have access to all parts
709 Next we make a resource group for our first real time task and give
716 Finally we move our first real time task into this resource group. We
718 on socket 0. Most uses of resource groups will also constrain which
732 For the same 2 socket system with memory b/w resource and CAT L3 the
765 Next we make a resource group for our real time cores and give it access
783 The resource groups in previous examples were all in the default "shareable"
784 mode allowing sharing of their cache allocations. If one resource group
785 configures a cache allocation then nothing prevents another resource group
788 In this example a new exclusive resource group will be created on a L2 CAT
790 capacity bitmask. The new exclusive resource group will be configured to use
803 We could attempt to create the new resource group at this point, but it will
815 To ensure that there is no overlap with another resource group the default
816 resource group's schemata has to change, making it possible for the new
817 resource group to become exclusive.
828 A new resource group will on creation not overlap with an exclusive resource
843 A resource group cannot be forced to overlap with an exclusive resource group::
862 removed from the default resource group's schemata::
870 Create a new resource group that will be associated with the pseudo-locked
878 On success the resource group's mode will change to pseudo-locked, the
964 1. Read the cbmmasks from each directory or the per-resource "bit_usage"
1092 The default resource group is unmodified, so we have access to all parts