mm/huge_memory.c: fix stale comments of transparent_hugepage_flags
Since commit13ece886d9
("thp: transparent hugepage config choice"), transparent hugepage support is disabled by default, and TRANSPARENT_HUGEPAGE_ALWAYS is configured when TRANSPARENT_HUGEPAGE=y. And since commitd39d33c332
("thp: enable direct defrag"), defrag is enable for all transparent hugepage page faults by default, not only in MADV_HUGEPAGE regions. Signed-off-by: Jianguo Wu <wujianguo@huawei.com> Reviewed-by: Wanpeng Li <liwanp@linux.vnet.ibm.com> Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
c69ded84a9
commit
8bfa3f9a01
|
@ -27,11 +27,12 @@
|
|||
#include "internal.h"
|
||||
|
||||
/*
|
||||
* By default transparent hugepage support is enabled for all mappings
|
||||
* and khugepaged scans all mappings. Defrag is only invoked by
|
||||
* khugepaged hugepage allocations and by page faults inside
|
||||
* MADV_HUGEPAGE regions to avoid the risk of slowing down short lived
|
||||
* allocations.
|
||||
* By default transparent hugepage support is disabled in order that avoid
|
||||
* to risk increase the memory footprint of applications without a guaranteed
|
||||
* benefit. When transparent hugepage support is enabled, is for all mappings,
|
||||
* and khugepaged scans all mappings.
|
||||
* Defrag is invoked by khugepaged hugepage allocations and by page faults
|
||||
* for all hugepage allocations.
|
||||
*/
|
||||
unsigned long transparent_hugepage_flags __read_mostly =
|
||||
#ifdef CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
|
||||
|
|
Loading…
Reference in New Issue