Lines Matching full:nodes

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