Lines Matching refs:nodes

45 abstractions called "nodes".  Linux maps the nodes onto the physical cells
47 architectures.  As with physical cells, software nodes may contain 0 or more
49 "closer" nodes--nodes that map to closer cells--will generally experience
60 the emulation of additional nodes.  For NUMA emulation, linux will carve up
61 the existing nodes--or the system memory for non-NUMA platforms--into multiple
62 nodes.  Each emulated node will manage a fraction of the underlying cells'
72 an ordered "zonelist".  A zonelist specifies the zones/nodes to visit when a
77 Because some nodes contain multiple zones containing different types of
93 nodes' zones in the selected zonelist looking for the first zone in the list
104 Thus, under sufficient imbalance, tasks can migrate between nodes, remote
114 System administrators can restrict the CPUs and nodes' memories that a non-
118 On architectures that do not hide memoryless nodes, Linux will include only
119 zones [nodes] with memory in the zonelists.  This means that for a memoryless
125 allows such allocations to fallback to other nearby nodes when a node that
142 If the architecture supports--does not hide--memoryless nodes, then CPUs
143 attached to memoryless nodes would always incur the fallback path overhead