Lines Matching +full:multi +full:- +full:subsystems

19 Each of the 'cells' may be viewed as an SMP [symmetric multi-processor] subset
20 of the system--although some components necessary for a stand-alone SMP system
22 connected together with some sort of system interconnect--e.g., a crossbar or
23 point-to-point link are common types of NUMA system interconnects.  Both of
43 [cache misses] to be to "local" memory--memory on the same cell, if any--or
53 "closer" nodes--nodes that map to closer cells--will generally experience
65 the existing nodes--or the system memory for non-NUMA platforms--into multiple
68 application features on non-NUMA platforms, and as a sort of memory resource
70 [see Documentation/admin-guide/cgroup-v1/cpusets.rst]
73 subsystem, complete with its own free page lists, in-use page lists, usage
98 "local" to the underlying physical resources and off the system interconnect--
101 NUMA topology of the platform--embodied in the "scheduling domains" data
102 structures [see Documentation/scheduler/sched-domains.rst]--and the scheduler
113 :ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`].
115 System administrators can restrict the CPUs and nodes' memories that a non-
117 using control groups and CPUsets.  [see Documentation/admin-guide/cgroup-v1/cpusets.rst]
121 node the "local memory node"--the node of the first zone in CPU's node's
122 zonelist--will not be the node itself.  Rather, it will be the node that the
143 If the architecture supports--does not hide--memoryless nodes, then CPUs
145 or some subsystems would fail to initialize if they attempted to allocated
147 architectures transparently, kernel subsystems can use the numa_mem_id()