linux-5.15/zone_type
をテンプレートにして作成
[
トップ
] [
新規
|
一覧
|
検索
|
最終更新
|
ヘルプ
|
ログイン
]
開始行:
*参照元 [#ff728978]
#backlinks
*説明 [#xba2c872]
-パス: [[linux-5.15/include/linux/mmzone.h]]
-FIXME: これは何？
--説明
**参考 [#b3e21e35]
*実装 [#z1e49345]
enum zone_type {
/*
* ZONE_DMA and ZONE_DMA32 are used when there are peri...
* to DMA to all of the addressable memory (ZONE_NORMAL).
* On architectures where this area covers the whole 32...
* space ZONE_DMA32 is used. ZONE_DMA is left for the o...
* DMA addressing constraints. This distinction is impo...
* DMA mask is assumed when ZONE_DMA32 is defined. Some...
* platforms may need both zones as they support periph...
* different DMA addressing limitations.
*/
#ifdef CONFIG_ZONE_DMA
ZONE_DMA,
#endif
#ifdef CONFIG_ZONE_DMA32
ZONE_DMA32,
#endif
/*
* Normal addressable memory is in ZONE_NORMAL. DMA ope...
* performed on pages in ZONE_NORMAL if the DMA devices...
* transfers to all addressable memory.
*/
ZONE_NORMAL,
#ifdef CONFIG_HIGHMEM
/*
* A memory area that is only addressable by the kernel...
* mapping portions into its own address space. This is...
* used by i386 to allow the kernel to address the memo...
* 900MB. The kernel will set up special mappings (page
* table entries on i386) for each page that the kernel...
* access.
*/
ZONE_HIGHMEM,
#endif
/*
* ZONE_MOVABLE is similar to ZONE_NORMAL, except that ...
* movable pages with few exceptional cases described b...
* cases for ZONE_MOVABLE are to make memory offlining/...
* likely to succeed, and to locally limit unmovable al...
* to increase the number of THP/huge pages. Notable sp...
*
* 1. Pinned pages: (long-term) pinning of movable page...
* essentially turn such pages unmovable. Therefore,...
* pinning long-term pages in ZONE_MOVABLE. When pag...
* faulted, they come from the right zone right away...
* still possible that address space already has pag...
* ZONE_MOVABLE at the time when pages are pinned (i...
* touches that memory before pinning). In such case...
* to a different zone. When migration fails - pinni...
* 2. memblock allocations: kernelcore/movablecore setu...
* situations where ZONE_MOVABLE contains unmovable ...
* after boot. Memory offlining and allocations fail...
* 3. Memory holes: kernelcore/movablecore setups might...
* situations where ZONE_MOVABLE contains memory hol...
* for example, if we have sections that are only pa...
* populated. Memory offlining and allocations fail ...
* 4. PG_hwpoison pages: while poisoned pages can be sk...
* memory offlining, such pages cannot be allocated.
* 5. Unmovable PG_offline pages: in paravirtualized en...
* hotplugged memory blocks might only partially be ...
* buddy (e.g., via XEN-balloon, Hyper-V balloon, vi...
* parts not manged by the buddy are unmovable PG_of...
* some cases (virtio-mem), such pages can be skippe...
* memory offlining, however, cannot be moved/alloca...
* techniques might use alloc_contig_range() to hide...
* exposed pages from the buddy again (e.g., to impl...
* of memory unplug in virtio-mem).
* 6. ZERO_PAGE(0), kernelcore/movablecore setups might...
* situations where ZERO_PAGE(0) which is allocated ...
* on different platforms may end up in a movable zo...
* cannot be migrated.
* 7. Memory-hotplug: when using memmap_on_memory and o...
* memory to the MOVABLE zone, the vmemmap pages are...
* such zone. Such pages cannot be really moved arou...
* self-stored in the range, but they are treated as...
* the range they describe is about to be offlined.
*
* In general, no unmovable allocations that degrade me...
* should end up in ZONE_MOVABLE. Allocators (like allo...
* have to expect that migrating pages in ZONE_MOVABLE ...
* if has_unmovable_pages() states that there are no un...
* there can be false negatives).
*/
ZONE_MOVABLE,
#ifdef CONFIG_ZONE_DEVICE
ZONE_DEVICE,
#endif
__MAX_NR_ZONES
};
*コメント [#me77bc9f]
終了行:
*参照元 [#ff728978]
#backlinks
*説明 [#xba2c872]
-パス: [[linux-5.15/include/linux/mmzone.h]]
-FIXME: これは何？
--説明
**参考 [#b3e21e35]
*実装 [#z1e49345]
enum zone_type {
/*
* ZONE_DMA and ZONE_DMA32 are used when there are peri...
* to DMA to all of the addressable memory (ZONE_NORMAL).
* On architectures where this area covers the whole 32...
* space ZONE_DMA32 is used. ZONE_DMA is left for the o...
* DMA addressing constraints. This distinction is impo...
* DMA mask is assumed when ZONE_DMA32 is defined. Some...
* platforms may need both zones as they support periph...
* different DMA addressing limitations.
*/
#ifdef CONFIG_ZONE_DMA
ZONE_DMA,
#endif
#ifdef CONFIG_ZONE_DMA32
ZONE_DMA32,
#endif
/*
* Normal addressable memory is in ZONE_NORMAL. DMA ope...
* performed on pages in ZONE_NORMAL if the DMA devices...
* transfers to all addressable memory.
*/
ZONE_NORMAL,
#ifdef CONFIG_HIGHMEM
/*
* A memory area that is only addressable by the kernel...
* mapping portions into its own address space. This is...
* used by i386 to allow the kernel to address the memo...
* 900MB. The kernel will set up special mappings (page
* table entries on i386) for each page that the kernel...
* access.
*/
ZONE_HIGHMEM,
#endif
/*
* ZONE_MOVABLE is similar to ZONE_NORMAL, except that ...
* movable pages with few exceptional cases described b...
* cases for ZONE_MOVABLE are to make memory offlining/...
* likely to succeed, and to locally limit unmovable al...
* to increase the number of THP/huge pages. Notable sp...
*
* 1. Pinned pages: (long-term) pinning of movable page...
* essentially turn such pages unmovable. Therefore,...
* pinning long-term pages in ZONE_MOVABLE. When pag...
* faulted, they come from the right zone right away...
* still possible that address space already has pag...
* ZONE_MOVABLE at the time when pages are pinned (i...
* touches that memory before pinning). In such case...
* to a different zone. When migration fails - pinni...
* 2. memblock allocations: kernelcore/movablecore setu...
* situations where ZONE_MOVABLE contains unmovable ...
* after boot. Memory offlining and allocations fail...
* 3. Memory holes: kernelcore/movablecore setups might...
* situations where ZONE_MOVABLE contains memory hol...
* for example, if we have sections that are only pa...
* populated. Memory offlining and allocations fail ...
* 4. PG_hwpoison pages: while poisoned pages can be sk...
* memory offlining, such pages cannot be allocated.
* 5. Unmovable PG_offline pages: in paravirtualized en...
* hotplugged memory blocks might only partially be ...
* buddy (e.g., via XEN-balloon, Hyper-V balloon, vi...
* parts not manged by the buddy are unmovable PG_of...
* some cases (virtio-mem), such pages can be skippe...
* memory offlining, however, cannot be moved/alloca...
* techniques might use alloc_contig_range() to hide...
* exposed pages from the buddy again (e.g., to impl...
* of memory unplug in virtio-mem).
* 6. ZERO_PAGE(0), kernelcore/movablecore setups might...
* situations where ZERO_PAGE(0) which is allocated ...
* on different platforms may end up in a movable zo...
* cannot be migrated.
* 7. Memory-hotplug: when using memmap_on_memory and o...
* memory to the MOVABLE zone, the vmemmap pages are...
* such zone. Such pages cannot be really moved arou...
* self-stored in the range, but they are treated as...
* the range they describe is about to be offlined.
*
* In general, no unmovable allocations that degrade me...
* should end up in ZONE_MOVABLE. Allocators (like allo...
* have to expect that migrating pages in ZONE_MOVABLE ...
* if has_unmovable_pages() states that there are no un...
* there can be false negatives).
*/
ZONE_MOVABLE,
#ifdef CONFIG_ZONE_DEVICE
ZONE_DEVICE,
#endif
__MAX_NR_ZONES
};
*コメント [#me77bc9f]
ページ名:
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
