224 lines · plain
1What: /sys/devices/system/node/possible2Date: October 20023Contact: Linux Memory Management list <linux-mm@kvack.org>4Description:5 Nodes that could be possibly become online at some point.6 7What: /sys/devices/system/node/online8Date: October 20029Contact: Linux Memory Management list <linux-mm@kvack.org>10Description:11 Nodes that are online.12 13What: /sys/devices/system/node/has_normal_memory14Date: October 200215Contact: Linux Memory Management list <linux-mm@kvack.org>16Description:17 Nodes that have regular memory.18 19What: /sys/devices/system/node/has_cpu20Date: October 200221Contact: Linux Memory Management list <linux-mm@kvack.org>22Description:23 Nodes that have one or more CPUs.24 25What: /sys/devices/system/node/has_high_memory26Date: October 200227Contact: Linux Memory Management list <linux-mm@kvack.org>28Description:29 Nodes that have regular or high memory.30 Depends on CONFIG_HIGHMEM.31 32What: /sys/devices/system/node/nodeX33Date: October 200234Contact: Linux Memory Management list <linux-mm@kvack.org>35Description:36 When CONFIG_NUMA is enabled, this is a directory containing37 information on node X such as what CPUs are local to the38 node. Each file is detailed next.39 40What: /sys/devices/system/node/nodeX/cpumap41Date: October 200242Contact: Linux Memory Management list <linux-mm@kvack.org>43Description:44 The node's cpumap.45 46What: /sys/devices/system/node/nodeX/cpulist47Date: October 200248Contact: Linux Memory Management list <linux-mm@kvack.org>49Description:50 The CPUs associated to the node.51 52What: /sys/devices/system/node/nodeX/meminfo53Date: October 200254Contact: Linux Memory Management list <linux-mm@kvack.org>55Description:56 Provides information about the node's distribution and memory57 utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.rst58 59What: /sys/devices/system/node/nodeX/numastat60Date: October 200261Contact: Linux Memory Management list <linux-mm@kvack.org>62Description:63 The node's hit/miss statistics, in units of pages.64 See Documentation/admin-guide/numastat.rst65 66What: /sys/devices/system/node/nodeX/distance67Date: October 200268Contact: Linux Memory Management list <linux-mm@kvack.org>69Description:70 Distance between the node and all the other nodes71 in the system.72 73What: /sys/devices/system/node/nodeX/vmstat74Date: October 200275Contact: Linux Memory Management list <linux-mm@kvack.org>76Description:77 The node's zoned virtual memory statistics.78 This is a superset of numastat.79 80What: /sys/devices/system/node/nodeX/compact81Date: February 201082Contact: Mel Gorman <mel@csn.ul.ie>83Description:84 When this file is written to, all memory within that node85 will be compacted. When it completes, memory will be freed86 into blocks which have as many contiguous pages as possible87 88What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/89Date: December 200990Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>91Description:92 The node's huge page size control/query attributes.93 See Documentation/admin-guide/mm/hugetlbpage.rst94 95What: /sys/devices/system/node/nodeX/accessY/96Date: December 201897Contact: Keith Busch <keith.busch@intel.com>98Description:99 The node's relationship to other nodes for access class "Y".100 101What: /sys/devices/system/node/nodeX/accessY/initiators/102Date: December 2018103Contact: Keith Busch <keith.busch@intel.com>104Description:105 The directory containing symlinks to memory initiator106 nodes that have class "Y" access to this target node's107 memory. CPUs and other memory initiators in nodes not in108 the list accessing this node's memory may have different109 performance.110 111What: /sys/devices/system/node/nodeX/accessY/targets/112Date: December 2018113Contact: Keith Busch <keith.busch@intel.com>114Description:115 The directory containing symlinks to memory targets that116 this initiator node has class "Y" access.117 118What: /sys/devices/system/node/nodeX/accessY/initiators/read_bandwidth119Date: December 2018120Contact: Keith Busch <keith.busch@intel.com>121Description:122 This node's read bandwidth in MB/s when accessed from123 nodes found in this access class's linked initiators.124 125What: /sys/devices/system/node/nodeX/accessY/initiators/read_latency126Date: December 2018127Contact: Keith Busch <keith.busch@intel.com>128Description:129 This node's read latency in nanoseconds when accessed130 from nodes found in this access class's linked initiators.131 132What: /sys/devices/system/node/nodeX/accessY/initiators/write_bandwidth133Date: December 2018134Contact: Keith Busch <keith.busch@intel.com>135Description:136 This node's write bandwidth in MB/s when accessed from137 found in this access class's linked initiators.138 139What: /sys/devices/system/node/nodeX/accessY/initiators/write_latency140Date: December 2018141Contact: Keith Busch <keith.busch@intel.com>142Description:143 This node's write latency in nanoseconds when access144 from nodes found in this class's linked initiators.145 146What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/147Date: December 2018148Contact: Keith Busch <keith.busch@intel.com>149Description:150 The directory containing attributes for the memory-side cache151 level 'Y'.152 153What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/indexing154Date: December 2018155Contact: Keith Busch <keith.busch@intel.com>156Description:157 The caches associativity indexing: 0 for direct mapped,158 non-zero if indexed.159 160What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/line_size161Date: December 2018162Contact: Keith Busch <keith.busch@intel.com>163Description:164 The number of bytes accessed from the next cache level on a165 cache miss.166 167What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/size168Date: December 2018169Contact: Keith Busch <keith.busch@intel.com>170Description:171 The size of this memory side cache in bytes.172 173What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/write_policy174Date: December 2018175Contact: Keith Busch <keith.busch@intel.com>176Description:177 The cache write policy: 0 for write-back, 1 for write-through,178 other or unknown.179 180What: /sys/devices/system/node/nodeX/x86/sgx_total_bytes181Date: November 2021182Contact: Jarkko Sakkinen <jarkko@kernel.org>183Description:184 The total amount of SGX physical memory in bytes.185 186What: /sys/devices/system/node/nodeX/memory_failure/total187Date: January 2023188Contact: Jiaqi Yan <jiaqiyan@google.com>189Description:190 The total number of raw poisoned pages (pages containing191 corrupted data due to memory errors) on a NUMA node.192 193What: /sys/devices/system/node/nodeX/memory_failure/ignored194Date: January 2023195Contact: Jiaqi Yan <jiaqiyan@google.com>196Description:197 Of the raw poisoned pages on a NUMA node, how many pages are198 ignored by memory error recovery attempt, usually because199 support for this type of pages is unavailable, and kernel200 gives up the recovery.201 202What: /sys/devices/system/node/nodeX/memory_failure/failed203Date: January 2023204Contact: Jiaqi Yan <jiaqiyan@google.com>205Description:206 Of the raw poisoned pages on a NUMA node, how many pages are207 failed by memory error recovery attempt. This usually means208 a key recovery operation failed.209 210What: /sys/devices/system/node/nodeX/memory_failure/delayed211Date: January 2023212Contact: Jiaqi Yan <jiaqiyan@google.com>213Description:214 Of the raw poisoned pages on a NUMA node, how many pages are215 delayed by memory error recovery attempt. Delayed poisoned216 pages usually will be retried by kernel.217 218What: /sys/devices/system/node/nodeX/memory_failure/recovered219Date: January 2023220Contact: Jiaqi Yan <jiaqiyan@google.com>221Description:222 Of the raw poisoned pages on a NUMA node, how many pages are223 recovered by memory error recovery attempt.224