Lines Matching refs:ZONE_MOVABLE
8 a focus on System RAM, including ZONE_MOVABLE support.
170 command line or if the memory block would intersect the ZONE_MOVABLE already.
173 ZONE_MOVABLE by::
222 Having the memory provided by memory block managed by ZONE_MOVABLE significantly
346 ``online_movable`` specifies onlining to ZONE_MOVABLE.
362 cannot be offlined. ``Movable`` indicates ZONE_MOVABLE.
397 set, the kernel will default to ZONE_MOVABLE, unless
432 ZONE_MOVABLE chapter
435 ZONE_MOVABLE is an important mechanism for more reliable memory offlining.
436 Further, having system RAM managed by ZONE_MOVABLE instead of one of the
445 movable. Such allocations can be served from ZONE_MOVABLE and the kernel zones.
447 Only movable allocations are served from ZONE_MOVABLE, resulting in unmovable
448 allocations being limited to the kernel zones. Without ZONE_MOVABLE, there is
454 Having too much system RAM managed by ZONE_MOVABLE is called a zone imbalance,
457 although there is still plenty of free memory left in ZONE_MOVABLE.
463 long-term pinning of pages, might not be able to deal with ZONE_MOVABLE at all.
468 ZONE_MOVABLE and similar considerations apply, especially when combining
469 CMA with ZONE_MOVABLE.
471 ZONE_MOVABLE Sizing Considerations
476 the normal case, ZONE_MOVABLE can be used when allocating such pages just fine.
479 managed by ZONE_MOVABLE. However, there are some things to consider when using
480 ZONE_MOVABLE, especially when fine-tuning zone ratios:
487 ZONE_MOVABLE. Only some implementations, such as virtio-balloon and
515 ZONE_MOVABLE, and therefore, memory offlining. Pinned pages cannot reside
516 on ZONE_MOVABLE as that would turn these pages unmovable. Therefore, they
518 even if there is plenty of free memory in ZONE_MOVABLE.
520 In addition, using ZONE_MOVABLE might make page pinning more expensive,
524 zones and ZONE_MOVABLE is not used.
526 To enable ZONE_MOVABLE to include the memory present at boot and to control the
531 Memory Offlining and ZONE_MOVABLE
534 Even with ZONE_MOVABLE, there are some corner cases where offlining a memory
569 when still encountering permanently unmovable pages within ZONE_MOVABLE