1 What: /sys/devices/system/node/possible 2 Date: October 2002 3 Contact: Linux Memory Management list <linux-mm@kvack.org> 4 Description: 5 Nodes that could be possibly become online at some point. 6 7 What: /sys/devices/system/node/online 8 Date: October 2002 9 Contact: Linux Memory Management list <linux-mm@kvack.org> 10 Description: 11 Nodes that are online. 12 13 What: /sys/devices/system/node/has_normal_memory 14 Date: October 2002 15 Contact: Linux Memory Management list <linux-mm@kvack.org> 16 Description: 17 Nodes that have regular memory. 18 19 What: /sys/devices/system/node/has_cpu 20 Date: October 2002 21 Contact: Linux Memory Management list <linux-mm@kvack.org> 22 Description: 23 Nodes that have one or more CPUs. 24 25 What: /sys/devices/system/node/has_high_memory 26 Date: October 2002 27 Contact: Linux Memory Management list <linux-mm@kvack.org> 28 Description: 29 Nodes that have regular or high memory. 30 Depends on CONFIG_HIGHMEM. 31 32 What: /sys/devices/system/node/nodeX 33 Date: October 2002 34 Contact: Linux Memory Management list <linux-mm@kvack.org> 35 Description: 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. 39 40 What: /sys/devices/system/node/nodeX/cpumap 41 Date: October 2002 42 Contact: Linux Memory Management list <linux-mm@kvack.org> 43 Description: 44 The node's cpumap. 45 46 What: /sys/devices/system/node/nodeX/cpulist 47 Date: October 2002 48 Contact: Linux Memory Management list <linux-mm@kvack.org> 49 Description: 50 The CPUs associated to the node. 51 52 What: /sys/devices/system/node/nodeX/meminfo 53 Date: October 2002 54 Contact: Linux Memory Management list <linux-mm@kvack.org> 55 Description: 56 Provides information about the node's distribution and memory 57 utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.rst 58 59 What: /sys/devices/system/node/nodeX/numastat 60 Date: October 2002 61 Contact: Linux Memory Management list <linux-mm@kvack.org> 62 Description: 63 The node's hit/miss statistics, in units of pages. 64 See Documentation/admin-guide/numastat.rst 65 66 What: /sys/devices/system/node/nodeX/distance 67 Date: October 2002 68 Contact: Linux Memory Management list <linux-mm@kvack.org> 69 Description: 70 Distance between the node and all the other nodes 71 in the system. 72 73 What: /sys/devices/system/node/nodeX/vmstat 74 Date: October 2002 75 Contact: Linux Memory Management list <linux-mm@kvack.org> 76 Description: 77 The node's zoned virtual memory statistics. 78 This is a superset of numastat. 79 80 What: /sys/devices/system/node/nodeX/compact 81 Date: February 2010 82 Contact: Mel Gorman <mel@csn.ul.ie> 83 Description: 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 87 88 What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/ 89 Date: December 2009 90 Contact: Lee Schermerhorn <lee.schermerhorn@hp.com> 91 Description: 92 The node's huge page size control/query attributes. 93 See Documentation/admin-guide/mm/hugetlbpage.rst 94 95 What: /sys/devices/system/node/nodeX/accessY/ 96 Date: December 2018 97 Contact: Keith Busch <keith.busch@intel.com> 98 Description: 99 The node's relationship to other nodes for access class "Y". 100 101 What: /sys/devices/system/node/nodeX/accessY/initiators/ 102 Date: December 2018 103 Contact: Keith Busch <keith.busch@intel.com> 104 Description: 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 109 performance. 110 111 What: /sys/devices/system/node/nodeX/accessY/targets/ 112 Date: December 2018 113 Contact: Keith Busch <keith.busch@intel.com> 114 Description: 115 The directory containing symlinks to memory targets that 116 this initiator node has class "Y" access. 117 118 What: /sys/devices/system/node/nodeX/accessY/initiators/read_bandwidth 119 Date: December 2018 120 Contact: Keith Busch <keith.busch@intel.com> 121 Description: 122 This node's read bandwidth in MB/s when accessed from 123 nodes found in this access class's linked initiators. 124 125 What: /sys/devices/system/node/nodeX/accessY/initiators/read_latency 126 Date: December 2018 127 Contact: Keith Busch <keith.busch@intel.com> 128 Description: 129 This node's read latency in nanoseconds when accessed 130 from nodes found in this access class's linked initiators. 131 132 What: /sys/devices/system/node/nodeX/accessY/initiators/write_bandwidth 133 Date: December 2018 134 Contact: Keith Busch <keith.busch@intel.com> 135 Description: 136 This node's write bandwidth in MB/s when accessed from 137 found in this access class's linked initiators. 138 139 What: /sys/devices/system/node/nodeX/accessY/initiators/write_latency 140 Date: December 2018 141 Contact: Keith Busch <keith.busch@intel.com> 142 Description: 143 This node's write latency in nanoseconds when access 144 from nodes found in this class's linked initiators. 145 146 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/ 147 Date: December 2018 148 Contact: Keith Busch <keith.busch@intel.com> 149 Description: 150 The directory containing attributes for the memory-side cache 151 level 'Y'. 152 153 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/indexing 154 Date: December 2018 155 Contact: Keith Busch <keith.busch@intel.com> 156 Description: 157 The caches associativity indexing: 0 for direct mapped, 158 non-zero if indexed. 159 160 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/line_size 161 Date: December 2018 162 Contact: Keith Busch <keith.busch@intel.com> 163 Description: 164 The number of bytes accessed from the next cache level on a 165 cache miss. 166 167 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/size 168 Date: December 2018 169 Contact: Keith Busch <keith.busch@intel.com> 170 Description: 171 The size of this memory side cache in bytes. 172 173 What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/write_policy 174 Date: December 2018 175 Contact: Keith Busch <keith.busch@intel.com> 176 Description: 177 The cache write policy: 0 for write-back, 1 for write-through, 178 other or unknown. 179 180 What: /sys/devices/system/node/nodeX/x86/sgx_total_bytes 181 Date: November 2021 182 Contact: Jarkko Sakkinen <jarkko@kernel.org> 183 Description: 184 The total amount of SGX physical memory in bytes. 185 186 What: /sys/devices/system/node/nodeX/memory_failure/total 187 Date: January 2023 188 Contact: Jiaqi Yan <jiaqiyan@google.com> 189 Description: 190 The total number of raw poisoned pages (pages containing 191 corrupted data due to memory errors) on a NUMA node. 192 193 What: /sys/devices/system/node/nodeX/memory_failure/ignored 194 Date: January 2023 195 Contact: Jiaqi Yan <jiaqiyan@google.com> 196 Description: 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. 201 202 What: /sys/devices/system/node/nodeX/memory_failure/failed 203 Date: January 2023 204 Contact: Jiaqi Yan <jiaqiyan@google.com> 205 Description: 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. 209 210 What: /sys/devices/system/node/nodeX/memory_failure/delayed 211 Date: January 2023 212 Contact: Jiaqi Yan <jiaqiyan@google.com> 213 Description: 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. 217 218 What: /sys/devices/system/node/nodeX/memory_failure/recovered 219 Date: January 2023 220 Contact: Jiaqi Yan <jiaqiyan@google.com> 221 Description: 222 Of the raw poisoned pages on a NUMA node, how many pages are 223 recovered by memory error recovery attempt.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.