|
@@ -30,7 +30,6 @@ Currently, these files are in /proc/sys/vm:
|
|
|
- dirty_writeback_centisecs
|
|
|
- drop_caches
|
|
|
- extfrag_threshold
|
|
|
-- hugepages_treat_as_movable
|
|
|
- hugetlb_shm_group
|
|
|
- laptop_mode
|
|
|
- legacy_va_layout
|
|
@@ -261,30 +260,6 @@ any throttling.
|
|
|
|
|
|
==============================================================
|
|
|
|
|
|
-hugepages_treat_as_movable
|
|
|
-
|
|
|
-This parameter controls whether we can allocate hugepages from ZONE_MOVABLE
|
|
|
-or not. If set to non-zero, hugepages can be allocated from ZONE_MOVABLE.
|
|
|
-ZONE_MOVABLE is created when kernel boot parameter kernelcore= is specified,
|
|
|
-so this parameter has no effect if used without kernelcore=.
|
|
|
-
|
|
|
-Hugepage migration is now available in some situations which depend on the
|
|
|
-architecture and/or the hugepage size. If a hugepage supports migration,
|
|
|
-allocation from ZONE_MOVABLE is always enabled for the hugepage regardless
|
|
|
-of the value of this parameter.
|
|
|
-IOW, this parameter affects only non-migratable hugepages.
|
|
|
-
|
|
|
-Assuming that hugepages are not migratable in your system, one usecase of
|
|
|
-this parameter is that users can make hugepage pool more extensible by
|
|
|
-enabling the allocation from ZONE_MOVABLE. This is because on ZONE_MOVABLE
|
|
|
-page reclaim/migration/compaction work more and you can get contiguous
|
|
|
-memory more likely. Note that using ZONE_MOVABLE for non-migratable
|
|
|
-hugepages can do harm to other features like memory hotremove (because
|
|
|
-memory hotremove expects that memory blocks on ZONE_MOVABLE are always
|
|
|
-removable,) so it's a trade-off responsible for the users.
|
|
|
-
|
|
|
-==============================================================
|
|
|
-
|
|
|
hugetlb_shm_group
|
|
|
|
|
|
hugetlb_shm_group contains group id that is allowed to create SysV
|