Lines Matching full:blocks

46 Memory sections are combined into chunks referred to as "memory blocks". The
51 All memory blocks have the same size.
59 (2) Onlining memory blocks
62 for the direct mapping, is allocated and initialized, and memory blocks are
64 blocks.
75 (1) Offlining memory blocks
83 In the second phase, the memory blocks are removed and metadata is freed.
109 blocks, and, if successful, hotunplug the memory from Linux.
122 Only complete memory blocks can be probed. Individual memory blocks are probed
136 Onlining and Offlining Memory Blocks
145 The Linux kernel can be configured to automatically online added memory blocks
146 and drivers automatically trigger offlining of memory blocks when trying
147 hotunplug of memory. Memory blocks can only be removed once offlining succeeded
148 and drivers may trigger offlining of memory blocks when attempting hotunplug of
151 Onlining Memory Blocks Manually
154 If auto-onlining of memory blocks isn't enabled, user-space has to manually
155 trigger onlining of memory blocks. Often, udev rules are used to automate this
182 Onlining Memory Blocks Automatically
185 The kernel can be configured to try auto-onlining of newly added memory blocks.
186 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
311   offlining of memory blocks.
317 onlined or offlined. All memory blocks have their device information located in
367 		    For online memory blocks, ``DMA``, ``DMA32``, ``Normal``,
370 		    multiple zones or spans multiple nodes; such memory blocks
374 		    For offline memory blocks, the first column shows the
459 				 blocks without specifying a target zone.
475 				 try onlining memory blocks to ZONE_MOVABLE if
496 				 As another example, as many memory blocks
499 				 special-casing units of memory blocks that can
503 				 change the zone of memory blocks dynamically
602 - Having a lot of offline memory blocks. Even offline memory blocks consume
604   memory blocks is not a typical case, though.
657 - Memory blocks with memory holes; this applies to memory blocks present during
658   boot and can apply to memory blocks hotplugged via the XEN balloon and the
662   offlining; this applies to memory blocks present during boot only.
664 - Special memory blocks prevented by the system from getting offlined. Examples
665   include any memory available during boot on arm64 or memory blocks spanning
666   the crashkernel area on s390x; this usually applies to memory blocks present
669 - Memory blocks overlapping with CMA areas cannot be offlined, this applies to
670   memory blocks present during boot only.