Lines Matching full:blocks

48 Memory sections are combined into chunks referred to as "memory blocks". The
53 All memory blocks have the same size.
61 (2) Onlining memory blocks
64 for the direct mapping, is allocated and initialized, and memory blocks are
66 blocks.
77 (1) Offlining memory blocks
85 In the second phase, the memory blocks are removed and metadata is freed.
111 blocks, and, if successful, hotunplug the memory from Linux.
124 Only complete memory blocks can be probed. Individual memory blocks are probed
138 Onlining and Offlining Memory Blocks
147 The Linux kernel can be configured to automatically online added memory blocks
148 and drivers automatically trigger offlining of memory blocks when trying
149 hotunplug of memory. Memory blocks can only be removed once offlining succeeded
150 and drivers may trigger offlining of memory blocks when attempting hotunplug of
153 Onlining Memory Blocks Manually
156 If auto-onlining of memory blocks isn't enabled, user-space has to manually
157 trigger onlining of memory blocks. Often, udev rules are used to automate this
185 Onlining Memory Blocks Automatically
188 The kernel can be configured to try auto-onlining of newly added memory blocks.
189 If this feature is disabled, the memory blocks will stay offline until
202 memory blocks only.
212   memory blocks; if onlining fails, memory blocks are removed again.
214 Offlining Memory Blocks
247 Observing the State of Memory Blocks
267 hot(un)plug and interact with memory blocks, especially, to online them.
280 		       blocks; configure auto-onlining.
286 		       See the ``state`` property of memory blocks for details.
288 ``probe``	       write-only: add (probe) selected memory blocks manually
302   offlining of memory blocks.
308 onlined or offlined. All memory blocks have their device information located in
358 		    For online memory blocks, ``DMA``, ``DMA32``, ``Normal``,
361 		    multiple zones or spans multiple nodes; such memory blocks
365 		    For offline memory blocks, the first column shows the
482 - Having a lot of offline memory blocks. Even offline memory blocks consume
484   memory blocks is not a typical case, though.
537 - Memory blocks with memory holes; this applies to memory blocks present during
538   boot and can apply to memory blocks hotplugged via the XEN balloon and the
542   offlining; this applies to memory blocks present during boot only.
544 - Special memory blocks prevented by the system from getting offlined. Examples
545   include any memory available during boot on arm64 or memory blocks spanning
546   the crashkernel area on s390x; this usually applies to memory blocks present
549 - Memory blocks overlapping with CMA areas cannot be offlined, this applies to
550   memory blocks present during boot only.