@@ -124,6 +124,13 @@ related to allocation:
124
124
"P":
125
125
Corresponding region is pseudo-locked. No
126
126
sharing allowed.
127
+ "sparse_masks":
128
+ Indicates if non-contiguous 1s value in CBM is supported.
129
+
130
+ "0":
131
+ Only contiguous 1s value in CBM is supported.
132
+ "1":
133
+ Non-contiguous 1s value in CBM is supported.
127
134
128
135
Memory bandwidth(MB) subdirectory contains the following files
129
136
with respect to allocation:
@@ -445,12 +452,13 @@ For cache resources we describe the portion of the cache that is available
445
452
for allocation using a bitmask. The maximum value of the mask is defined
446
453
by each cpu model (and may be different for different cache levels). It
447
454
is found using CPUID, but is also provided in the "info" directory of
448
- the resctrl file system in "info/{resource}/cbm_mask". Intel hardware
455
+ the resctrl file system in "info/{resource}/cbm_mask". Some Intel hardware
449
456
requires that these masks have all the '1' bits in a contiguous block. So
450
457
0x3, 0x6 and 0xC are legal 4-bit masks with two bits set, but 0x5, 0x9
451
- and 0xA are not. On a system with a 20-bit mask each bit represents 5%
452
- of the capacity of the cache. You could partition the cache into four
453
- equal parts with masks: 0x1f, 0x3e0, 0x7c00, 0xf8000.
458
+ and 0xA are not. Check /sys/fs/resctrl/info/{resource}/sparse_masks
459
+ if non-contiguous 1s value is supported. On a system with a 20-bit mask
460
+ each bit represents 5% of the capacity of the cache. You could partition
461
+ the cache into four equal parts with masks: 0x1f, 0x3e0, 0x7c00, 0xf8000.
454
462
455
463
Memory bandwidth Allocation and monitoring
456
464
==========================================
0 commit comments