mm-document-semantics-of-zone_movable.patch removed from -mm tree
The patch titled
Subject: mm: document semantics of ZONE_MOVABLE
has been removed from the -mm tree. Its filename was
mm-document-semantics-of-zone_movable.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: David Hildenbrand <[email protected]>
Subject: mm: document semantics of ZONE_MOVABLE
Let's document what ZONE_MOVABLE means, how it's used, and which special cases we have regarding unmovable pages (memory offlining vs. migration / allocations).
---
include/linux/mmzone.h | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+)
include/linux/mmzone.h renamed from include/linux/mmzone.h~mm-document-semantics-of-zone_movable +35 -0
@@ -396,6 +396,41 @@ enum zone_type {*/ ZONE_HIGHMEM,#endif +/* +* ZONE_MOVABLE is similar to ZONE_NORMAL, except that it contains +* movable pages with few exceptional cases described below. Main use +* cases for ZONE_MOVABLE are to make memory offlining/unplug more +* likely to succeed, and to locally limit unmovable allocations - e.g., +* to increase the number of THP/huge pages. Notable special cases are: +* +* 1. Pinned pages: (long-term) pinning of movable pages might +* essentially turn such pages unmovable. Memory offlining might +* retry a long time. +* 2. memblock allocations: kernelcore/movablecore setups might create +* situations where ZONE_MOVABLE contains unmovable allocations +* after boot. Memory offlining and allocations fail early. +* 3. Memory holes: kernelcore/movablecore setups might create very rare +* situations where ZONE_MOVABLE contains memory holes after boot, +* for example, if we have sections that are only partially +* populated. Memory offlining and allocations fail early. +* 4. PG_hwpoison pages: while poisoned pages can be skipped during +* memory offlining, such pages cannot be allocated. +* 5. Unmovable PG_offline pages: in paravirtualized environments, +* hotplugged memory blocks might only partially be managed by the +* buddy (e.g., via XEN-balloon, Hyper-V balloon, virtio-mem). The +* parts not manged by the buddy are unmovable PG_offline pages. In +* some cases (virtio-mem), such pages can be skipped during +* memory offlining, however, cannot be moved/allocated. These +* techniques might use alloc_contig_range() to hide previously +* exposed pages from the buddy again (e.g., to implement some sort +* of memory unplug in virtio-mem). +* +* In general, no unmovable allocations that degrade memory offlining +* should end up in ZONE_MOVABLE. Allocators (like alloc_contig_range()) +* have to expect that migrating pages in ZONE_MOVABLE can fail (even +* if has_unmovable_pages() states that there are no unmovable pages, +* there can be false negatives). +*/ ZONE_MOVABLE,#ifdef CONFIG_ZONE_DEVICE ZONE_DEVICE,
_
Patches currently in -mm which might be from [email protected] are
mm-memory_hotplug-inline-__offline_pages-into-offline_pages.patch mm-memory_hotplug-enforce-section-granularity-when-onlining-offlining.patch mm-memory_hotplug-simplify-page-offlining.patch mm-page_alloc-simplify-__offline_isolated_pages.patch mm-memory_hotplug-drop-nr_isolate_pageblock-in-offline_pages.patch mm-page_isolation-simplify-return-value-of-start_isolate_page_range.patch mm-memory_hotplug-simplify-page-onlining.patch mm-page_alloc-drop-stale-pageblock-comment-in-memmap_init_zone.patch mm-pass-migratetype-into-memmap_init_zone-and-move_pfn_range_to_zone.patch mm-memory_hotplug-mark-pageblocks-migrate_isolate-while-onlining-memory.patch kernel-resource-make-release_mem_region_adjustable-never-fail.patch kernel-resource-move-and-rename-ioresource_mem_driver_managed.patch mm-memory_hotplug-guard-more-declarations-by-config_memory_hotplug.patch mm-memory_hotplug-prepare-passing-flags-to-add_memory-and-friends.patch mm-memory_hotplug-memhp_merge_resource-to-specify-merging-of-system-ram-resources.patch virtio-mem-try-to-merge-system-ram-resources.patch xen-balloon-try-to-merge-system-ram-resources.patch hv_balloon-try-to-merge-system-ram-resources.patch kernel-resource-make-iomem_resource-implicit-in-release_mem_region_adjustable.patch mm-page_alloc-convert-report-flag-of-__free_one_page-to-a-proper-flag.patch mm-page_alloc-place-pages-to-tail-in-__putback_isolated_page.patch mm-page_alloc-move-pages-to-tail-in-move_to_free_list.patch mm-page_alloc-place-pages-to-tail-in-__free_pages_core.patch mm-memory_hotplug-update-comment-regarding-zone-shuffling.patch