Lines Matching refs:ZONE_MOVABLE
6 a focus on System RAM, including ZONE_MOVABLE support.
170 ZONE_MOVABLE by::
222 Having the memory provided by memory block managed by ZONE_MOVABLE significantly
355 ``online_movable`` specifies onlining to ZONE_MOVABLE.
371 cannot be offlined. ``Movable`` indicates ZONE_MOVABLE.
407 set, the kernel will default to ZONE_MOVABLE when
470 command line parameter: default to ZONE_MOVABLE
475 try onlining memory blocks to ZONE_MOVABLE if
494 completely to ZONE_MOVABLE or completely to
498 onlined to ZONE_MOVABLE as possible,
502 problematic with ZONE_MOVABLE and does not
521 memory to ZONE_MOVABLE in many setups. The
528 ZONE_MOVABLE memory for a different memory
532 ZONE_MOVABLE automatically. In contrast, memory
535 ZONE_MOVABLE memory within *the same*
546 completely to ZONE_MOVABLE automatically if
552 ZONE_MOVABLE chapter
555 ZONE_MOVABLE is an important mechanism for more reliable memory offlining.
556 Further, having system RAM managed by ZONE_MOVABLE instead of one of the
565 movable. Such allocations can be served from ZONE_MOVABLE and the kernel zones.
567 Only movable allocations are served from ZONE_MOVABLE, resulting in unmovable
568 allocations being limited to the kernel zones. Without ZONE_MOVABLE, there is
574 Having too much system RAM managed by ZONE_MOVABLE is called a zone imbalance,
577 although there is still plenty of free memory left in ZONE_MOVABLE.
583 long-term pinning of pages, might not be able to deal with ZONE_MOVABLE at all.
588 ZONE_MOVABLE and similar considerations apply, especially when combining
589 CMA with ZONE_MOVABLE.
591 ZONE_MOVABLE Sizing Considerations
596 the normal case, ZONE_MOVABLE can be used when allocating such pages just fine.
599 managed by ZONE_MOVABLE. However, there are some things to consider when using
600 ZONE_MOVABLE, especially when fine-tuning zone ratios:
607 ZONE_MOVABLE. Only some implementations, such as virtio-balloon and
635 ZONE_MOVABLE, and therefore, memory offlining. Pinned pages cannot reside
636 on ZONE_MOVABLE as that would turn these pages unmovable. Therefore, they
638 even if there is plenty of free memory in ZONE_MOVABLE.
640 In addition, using ZONE_MOVABLE might make page pinning more expensive,
644 zones and ZONE_MOVABLE is not used.
646 To enable ZONE_MOVABLE to include the memory present at boot and to control the
651 Memory Offlining and ZONE_MOVABLE
654 Even with ZONE_MOVABLE, there are some corner cases where offlining a memory
689 when still encountering permanently unmovable pages within ZONE_MOVABLE