summaryrefslogtreecommitdiffstats
path: root/Documentation/sysctl
diff options
context:
space:
mode:
authorMichal Hocko <mhocko@suse.com>2018-01-31 19:17:10 -0500
committerLinus Torvalds <torvalds@linux-foundation.org>2018-01-31 20:18:37 -0500
commitd6cb41cc44c63492702281b1d329955ca767d399 (patch)
tree785e8c630913c6408b6a9e2d487aa06209ec0785 /Documentation/sysctl
parenta4ef87684108e5fef38cf289ee360f9b87a53cfd (diff)
mm, hugetlb: remove hugepages_treat_as_movable sysctl
hugepages_treat_as_movable has been introduced by 396faf0303d2 ("Allow huge page allocations to use GFP_HIGH_MOVABLE") to allow hugetlb allocations from ZONE_MOVABLE even when hugetlb pages were not migrateable. The purpose of the movable zone was different at the time. It aimed at reducing memory fragmentation and hugetlb pages being long lived and large werre not contributing to the fragmentation so it was acceptable to use the zone back then. Things have changed though and the primary purpose of the zone became migratability guarantee. If we allow non migrateable hugetlb pages to be in ZONE_MOVABLE memory hotplug might fail to offline the memory. Remove the knob and only rely on hugepage_migration_supported to allow movable zones. Mel said: : Primarily it was aimed at allowing the hugetlb pool to safely shrink with : the ability to grow it again. The use case was for batched jobs, some of : which needed huge pages and others that did not but didn't want the memory : useless pinned in the huge pages pool. : : I suspect that more users rely on THP than hugetlbfs for flexible use of : huge pages with fallback options so I think that removing the option : should be ok. Link: http://lkml.kernel.org/r/20171003072619.8654-1-mhocko@kernel.org Signed-off-by: Michal Hocko <mhocko@suse.com> Reported-by: Alexandru Moise <00moses.alexander00@gmail.com> Acked-by: Mel Gorman <mgorman@suse.de> Cc: Alexandru Moise <00moses.alexander00@gmail.com> Cc: Mike Kravetz <mike.kravetz@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/sysctl')
-rw-r--r--Documentation/sysctl/vm.txt25
1 files changed, 0 insertions, 25 deletions
diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt
index 5025ff9307e6..ff234d229cbb 100644
--- a/Documentation/sysctl/vm.txt
+++ b/Documentation/sysctl/vm.txt
@@ -30,7 +30,6 @@ Currently, these files are in /proc/sys/vm:
30- dirty_writeback_centisecs 30- dirty_writeback_centisecs
31- drop_caches 31- drop_caches
32- extfrag_threshold 32- extfrag_threshold
33- hugepages_treat_as_movable
34- hugetlb_shm_group 33- hugetlb_shm_group
35- laptop_mode 34- laptop_mode
36- legacy_va_layout 35- legacy_va_layout
@@ -261,30 +260,6 @@ any throttling.
261 260
262============================================================== 261==============================================================
263 262
264hugepages_treat_as_movable
265
266This parameter controls whether we can allocate hugepages from ZONE_MOVABLE
267or not. If set to non-zero, hugepages can be allocated from ZONE_MOVABLE.
268ZONE_MOVABLE is created when kernel boot parameter kernelcore= is specified,
269so this parameter has no effect if used without kernelcore=.
270
271Hugepage migration is now available in some situations which depend on the
272architecture and/or the hugepage size. If a hugepage supports migration,
273allocation from ZONE_MOVABLE is always enabled for the hugepage regardless
274of the value of this parameter.
275IOW, this parameter affects only non-migratable hugepages.
276
277Assuming that hugepages are not migratable in your system, one usecase of
278this parameter is that users can make hugepage pool more extensible by
279enabling the allocation from ZONE_MOVABLE. This is because on ZONE_MOVABLE
280page reclaim/migration/compaction work more and you can get contiguous
281memory more likely. Note that using ZONE_MOVABLE for non-migratable
282hugepages can do harm to other features like memory hotremove (because
283memory hotremove expects that memory blocks on ZONE_MOVABLE are always
284removable,) so it's a trade-off responsible for the users.
285
286==============================================================
287
288hugetlb_shm_group 263hugetlb_shm_group
289 264
290hugetlb_shm_group contains group id that is allowed to create SysV 265hugetlb_shm_group contains group id that is allowed to create SysV