Lines Matching +full:auto +full:- +full:boot
22 - The physical memory available to a machine can be adjusted at runtime, up- or
27 - Replacing hardware, such as DIMMs or whole NUMA nodes, without downtime. One
30 - Reducing energy consumption either by physically unplugging memory modules or
34 used to expose persistent memory, other performance-differentiated memory and
41 ------------------------------
56 ------------------------
73 --------------------------
96 ------------------
114 --------------
154 -------------------------------
156 If auto-onlining of memory blocks isn't enabled, user-space has to manually
185 ------------------------------------
187 The kernel can be configured to try auto-onlining of newly added memory blocks.
191 The configured auto-online behavior can be observed via::
195 Auto-onlining can be enabled by writing ``online``, ``online_kernel`` or
203 Modifying the auto-online behavior will only affect all subsequently added
208 In corner cases, auto-onlining can fail. The kernel won't retry. Note that
209 auto-onlining is not expected to fail in default configurations.
217 -----------------------
250 ------------------------------------
252 The state (online/offline/going-offline) of a memory block can be observed
272 ------------------------------------------
281 ``auto_online_blocks`` read-write: set or get the default state of new memory
282 blocks; configure auto-onlining.
289 ``block_size_bytes`` read-only: the size in bytes of a memory block.
290 ``probe`` write-only: add (probe) selected memory blocks manually
295 ``uevent`` read-write: generic udev file for device subsystems.
307 ------------------------------------
332 ``online`` read-write: simplified interface to trigger onlining /
335 ``phys_device`` read-only: legacy interface only ever used on s390x to
337 ``phys_index`` read-only: the memory block id (XXX).
338 ``removable`` read-only: legacy interface that indicated whether a memory
342 ``state`` read-write: advanced interface to trigger onlining /
353 When reading, ``online``, ``offline`` and ``going-offline``
355 ``uevent`` read-write: generic uevent file for devices.
356 ``valid_zones`` read-only: when a block is online, shows the zone it
383 /sys/devices/system/node/node0/memory9 -> ../../memory/memory9
387 /sys/devices/system/memory/memory9/node0 -> ../../node/node0
390 -----------------------
396 ``memhp_default_state`` configure auto-onlining by essentially setting
399 using the ``contig-zones`` online policy. When
405 See Documentation/admin-guide/kernel-parameters.txt for a more generic
409 ------------------
425 ``memmap_on_memory`` read-write: Allocate memory for the memmap from
438 ``online_policy`` read-write: Set the basic policy used for
441 ``contig-zones`` has been the kernel default
447 When set to ``contig-zones``, the kernel will
455 When set to ``auto-movable``, the kernel will
469 firmware-provided memory map early during boot
471 added and onlined later during boot (such as
472 done by virtio-mem or by some hypervisors
478 belonging to a virtio-mem device will be
480 special-casing units of memory blocks that can
486 ``auto_movable_ratio`` read-write: Set the maximum MOVABLE:KERNEL
487 memory ratio in % for the ``auto-movable``
514 hotplugged by a virtio-mem device that got
517 virtio-mem device.
518 ``auto_movable_numa_aware`` read-write: Configure whether the
519 ``auto_movable_ratio`` in the ``auto-movable``
553 ---------------
564 long-term pinning of pages, might not be able to deal with ZONE_MOVABLE at all.
573 ----------------------------------
581 ZONE_MOVABLE, especially when fine-tuning zone ratios:
583 - Having a lot of offline memory blocks. Even offline memory blocks consume
587 - Memory ballooning without balloon compaction is incompatible with
588 ZONE_MOVABLE. Only some implementations, such as virtio-balloon and
596 - Gigantic pages are unmovable, resulting in user space consuming a
599 - Huge pages are unmovable when an architectures does not support huge
602 - Page tables are unmovable. Excessive swapping, mapping extremely large
608 - In certain DAX configurations the memory map for the device memory will be
611 - KASAN can have a significant memory overhead, for example, consuming 1/8th of
614 - Long-term pinning of pages. Techniques that rely on long-term pinnings
624 By default, all the memory configured at boot time is managed by the kernel
627 To enable ZONE_MOVABLE to include the memory present at boot and to control the
630 Documentation/admin-guide/kernel-parameters.rst for their description.
633 ---------------------------------
638 - Memory blocks with memory holes; this applies to memory blocks present during
639 boot and can apply to memory blocks hotplugged via the XEN balloon and the
640 Hyper-V balloon.
642 - Mixed NUMA nodes and mixed zones within a single memory block prevent memory
643 offlining; this applies to memory blocks present during boot only.
645 - Special memory blocks prevented by the system from getting offlined. Examples
646 include any memory available during boot on arm64 or memory blocks spanning
648 during boot only.
650 - Memory blocks overlapping with CMA areas cannot be offlined, this applies to
651 memory blocks present during boot only.
653 - Concurrent activity that operates on the same physical memory area, such as
656 - Out of memory when dissolving huge pages, especially when HugeTLB Vmemmap
671 (-> BUG), memory offlining will keep retrying until it eventually succeeds.