Lines Matching +full:directory +full:- +full:based

13 under different domains, or "nodes", based on locality and performance
20  +------------------+     +------------------+
21  | Compute Node 0   +-----+ Compute Node 1   |
23  +--------+---------+     +--------+---------+
25  +--------+---------+     +--------+---------+
27  +------------------+     +--------+---------+
35 performance when accessing a given memory target. Each initiator-target
47 	# symlinks -v /sys/devices/system/node/nodeX/access0/targets/
48 	relative: /sys/devices/system/node/nodeX/access0/targets/nodeY -> ../../nodeY
50 	# symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
51 	relative: /sys/devices/system/node/nodeY/access0/initiators/nodeX -> ../../nodeX
69 be allocated from based on the node's performance characteristics. If
71 node sysfs hierarchy by appending the attributes directory under the
82 	# tree -P "read*|write*" /sys/devices/system/node/nodeY/access0/initiators/
84 	|-- read_bandwidth
85 	|-- read_latency
86 	|-- write_bandwidth
87 	`-- write_latency
117 L1, L2, L3) uses the CPU-side view where each increased level is lower
122 The memory-side caches are not directly addressable by software. When
136 will create the following directory::
140 If that directory is not present, the system either does not provide
141 a memory-side cache, or that information is not accessible to the kernel.
150 Each cache level's directory provides its attributes. For example, the
156 	|-- index1
157 	|   |-- indexing
158 	|   |-- line_size
159 	|   |-- size
160 	|   `-- write_policy
162 The "indexing" will be 0 if it is a direct-mapped cache, and non-zero
163 for any other indexed based, multi-way associativity.
170 The "write_policy" will be 0 for write-back, and non-zero for
171 write-through caching.
178 - Section 5.2.27