1 What: /sys/devices/system/node/possible
3 Contact: Linux Memory Management list <linux-mm@kvack.org>
5 Nodes that could be possibly become online at some point.
7 What: /sys/devices/system/node/online
9 Contact: Linux Memory Management list <linux-mm@kvack.org>
11 Nodes that are online.
13 What: /sys/devices/system/node/has_normal_memory
15 Contact: Linux Memory Management list <linux-mm@kvack.org>
17 Nodes that have regular memory.
19 What: /sys/devices/system/node/has_cpu
21 Contact: Linux Memory Management list <linux-mm@kvack.org>
23 Nodes that have one or more CPUs.
25 What: /sys/devices/system/node/has_high_memory
27 Contact: Linux Memory Management list <linux-mm@kvack.org>
29 Nodes that have regular or high memory.
30 Depends on CONFIG_HIGHMEM.
32 What: /sys/devices/system/node/nodeX
34 Contact: Linux Memory Management list <linux-mm@kvack.org>
36 When CONFIG_NUMA is enabled, this is a directory containing
37 information on node X such as what CPUs are local to the
38 node. Each file is detailed next.
40 What: /sys/devices/system/node/nodeX/cpumap
42 Contact: Linux Memory Management list <linux-mm@kvack.org>
46 What: /sys/devices/system/node/nodeX/cpulist
48 Contact: Linux Memory Management list <linux-mm@kvack.org>
50 The CPUs associated to the node.
52 What: /sys/devices/system/node/nodeX/meminfo
54 Contact: Linux Memory Management list <linux-mm@kvack.org>
56 Provides information about the node's distribution and memory
57 utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.rst
59 What: /sys/devices/system/node/nodeX/numastat
61 Contact: Linux Memory Management list <linux-mm@kvack.org>
63 The node's hit/miss statistics, in units of pages.
64 See Documentation/admin-guide/numastat.rst
66 What: /sys/devices/system/node/nodeX/distance
68 Contact: Linux Memory Management list <linux-mm@kvack.org>
70 Distance between the node and all the other nodes
73 What: /sys/devices/system/node/nodeX/vmstat
75 Contact: Linux Memory Management list <linux-mm@kvack.org>
77 The node's zoned virtual memory statistics.
78 This is a superset of numastat.
80 What: /sys/devices/system/node/nodeX/compact
82 Contact: Mel Gorman <mel@csn.ul.ie>
84 When this file is written to, all memory within that node
85 will be compacted. When it completes, memory will be freed
86 into blocks which have as many contiguous pages as possible
88 What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
90 Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>
92 The node's huge page size control/query attributes.
93 See Documentation/admin-guide/mm/hugetlbpage.rst
95 What: /sys/devices/system/node/nodeX/accessY/
97 Contact: Keith Busch <keith.busch@intel.com>
99 The node's relationship to other nodes for access class "Y".
101 What: /sys/devices/system/node/nodeX/accessY/initiators/
103 Contact: Keith Busch <keith.busch@intel.com>
105 The directory containing symlinks to memory initiator
106 nodes that have class "Y" access to this target node's
107 memory. CPUs and other memory initiators in nodes not in
108 the list accessing this node's memory may have different
111 What: /sys/devices/system/node/nodeX/accessY/targets/
113 Contact: Keith Busch <keith.busch@intel.com>
115 The directory containing symlinks to memory targets that
116 this initiator node has class "Y" access.
118 What: /sys/devices/system/node/nodeX/accessY/initiators/read_bandwidth
120 Contact: Keith Busch <keith.busch@intel.com>
122 This node's read bandwidth in MB/s when accessed from
123 nodes found in this access class's linked initiators.
125 What: /sys/devices/system/node/nodeX/accessY/initiators/read_latency
127 Contact: Keith Busch <keith.busch@intel.com>
129 This node's read latency in nanoseconds when accessed
130 from nodes found in this access class's linked initiators.
132 What: /sys/devices/system/node/nodeX/accessY/initiators/write_bandwidth
134 Contact: Keith Busch <keith.busch@intel.com>
136 This node's write bandwidth in MB/s when accessed from
137 found in this access class's linked initiators.
139 What: /sys/devices/system/node/nodeX/accessY/initiators/write_latency
141 Contact: Keith Busch <keith.busch@intel.com>
143 This node's write latency in nanoseconds when access
144 from nodes found in this class's linked initiators.
146 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/
148 Contact: Keith Busch <keith.busch@intel.com>
150 The directory containing attributes for the memory-side cache
153 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/indexing
155 Contact: Keith Busch <keith.busch@intel.com>
157 The caches associativity indexing: 0 for direct mapped,
160 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/line_size
162 Contact: Keith Busch <keith.busch@intel.com>
164 The number of bytes accessed from the next cache level on a
167 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/size
169 Contact: Keith Busch <keith.busch@intel.com>
171 The size of this memory side cache in bytes.
173 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/write_policy
175 Contact: Keith Busch <keith.busch@intel.com>
177 The cache write policy: 0 for write-back, 1 for write-through,
180 What: /sys/devices/system/node/nodeX/x86/sgx_total_bytes
182 Contact: Jarkko Sakkinen <jarkko@kernel.org>
184 The total amount of SGX physical memory in bytes.
186 What: /sys/devices/system/node/nodeX/memory_failure/total
188 Contact: Jiaqi Yan <jiaqiyan@google.com>
190 The total number of raw poisoned pages (pages containing
191 corrupted data due to memory errors) on a NUMA node.
193 What: /sys/devices/system/node/nodeX/memory_failure/ignored
195 Contact: Jiaqi Yan <jiaqiyan@google.com>
197 Of the raw poisoned pages on a NUMA node, how many pages are
198 ignored by memory error recovery attempt, usually because
199 support for this type of pages is unavailable, and kernel
200 gives up the recovery.
202 What: /sys/devices/system/node/nodeX/memory_failure/failed
204 Contact: Jiaqi Yan <jiaqiyan@google.com>
206 Of the raw poisoned pages on a NUMA node, how many pages are
207 failed by memory error recovery attempt. This usually means
208 a key recovery operation failed.
210 What: /sys/devices/system/node/nodeX/memory_failure/delayed
212 Contact: Jiaqi Yan <jiaqiyan@google.com>
214 Of the raw poisoned pages on a NUMA node, how many pages are
215 delayed by memory error recovery attempt. Delayed poisoned
216 pages usually will be retried by kernel.
218 What: /sys/devices/system/node/nodeX/memory_failure/recovered
220 Contact: Jiaqi Yan <jiaqiyan@google.com>
222 Of the raw poisoned pages on a NUMA node, how many pages are
223 recovered by memory error recovery attempt.