Documentation/mm/numa.rst

47 abstractions called "nodes".  Linux maps the nodes onto the physical cells
49 architectures.  As with physical cells, software nodes may contain 0 or more
51 "closer" nodes--nodes that map to closer cells--will generally experience
62 the emulation of additional nodes.  For NUMA emulation, linux will carve up
63 the existing nodes--or the system memory for non-NUMA platforms--into multiple
64 nodes.  Each emulated node will manage a fraction of the underlying cells'
74 an ordered "zonelist".  A zonelist specifies the zones/nodes to visit when a
79 Because some nodes contain multiple zones containing different types of
85 from the same node before using remote nodes which are ordered by NUMA distance.
92 nodes' zones in the selected zonelist looking for the first zone in the list
103 Thus, under sufficient imbalance, tasks can migrate between nodes, remote
113 System administrators can restrict the CPUs and nodes' memories that a non-
117 On architectures that do not hide memoryless nodes, Linux will include only
118 zones [nodes] with memory in the zonelists.  This means that for a memoryless
124 allows such allocations to fallback to other nearby nodes when a node that
141 If the architecture supports--does not hide--memoryless nodes, then CPUs
142 attached to memoryless nodes would always incur the fallback path overhead