Lines Matching refs:ZONE_MOVABLE

8 a focus on System RAM, including ZONE_MOVABLE support.
172 ZONE_MOVABLE by::
224 Having the memory provided by memory block managed by ZONE_MOVABLE significantly
348 		    ``online_movable`` specifies onlining to ZONE_MOVABLE.
364 		    cannot be offlined. ``Movable`` indicates ZONE_MOVABLE.
400 			 set, the kernel will default to ZONE_MOVABLE when
451 				 command line parameter: default to ZONE_MOVABLE
456 				 try onlining memory blocks to ZONE_MOVABLE if
475 				 completely to ZONE_MOVABLE or completely to
479 				 onlined to ZONE_MOVABLE as possible,
483 				 problematic with ZONE_MOVABLE and does not
502 				 memory to ZONE_MOVABLE in many setups. The
509 				 ZONE_MOVABLE memory for a different memory
513 				 ZONE_MOVABLE automatically. In contrast, memory
516 				 ZONE_MOVABLE memory within *the same*
527 				 completely to ZONE_MOVABLE automatically if
533 ZONE_MOVABLE  chapter
536 ZONE_MOVABLE is an important mechanism for more reliable memory offlining.
537 Further, having system RAM managed by ZONE_MOVABLE instead of one of the
546 movable. Such allocations can be served from ZONE_MOVABLE and the kernel zones.
548 Only movable allocations are served from ZONE_MOVABLE, resulting in unmovable
549 allocations being limited to the kernel zones. Without ZONE_MOVABLE, there is
555 Having too much system RAM managed by ZONE_MOVABLE is called a zone imbalance,
558 although there is still plenty of free memory left in ZONE_MOVABLE.
564 long-term pinning of pages, might not be able to deal with ZONE_MOVABLE at all.
569   ZONE_MOVABLE and similar considerations apply, especially when combining
570   CMA with ZONE_MOVABLE.
572 ZONE_MOVABLE Sizing Considerations
577 the normal case, ZONE_MOVABLE can be used when allocating such pages just fine.
580 managed by ZONE_MOVABLE. However, there are some things to consider when using
581 ZONE_MOVABLE, especially when fine-tuning zone ratios:
588   ZONE_MOVABLE. Only some implementations, such as virtio-balloon and
616   ZONE_MOVABLE, and therefore, memory offlining. Pinned pages cannot reside
617   on ZONE_MOVABLE as that would turn these pages unmovable. Therefore, they
619   even if there is plenty of free memory in ZONE_MOVABLE.
621   In addition, using ZONE_MOVABLE might make page pinning more expensive,
625 zones and ZONE_MOVABLE is not used.
627 To enable ZONE_MOVABLE to include the memory present at boot and to control the
632 Memory Offlining and ZONE_MOVABLE
635 Even with ZONE_MOVABLE, there are some corner cases where offlining a memory
670 when still encountering permanently unmovable pages within ZONE_MOVABLE