Commit 8bfa3f9a authored by Jianguo Wu's avatar Jianguo Wu Committed by Linus Torvalds
Browse files

mm/huge_memory.c: fix stale comments of transparent_hugepage_flags 



Since commit 13ece886 ("thp: transparent hugepage config choice"),
transparent hugepage support is disabled by default, and
TRANSPARENT_HUGEPAGE_ALWAYS is configured when TRANSPARENT_HUGEPAGE=y.

And since commit d39d33c3 ("thp: enable direct defrag"), defrag is
enable for all transparent hugepage page faults by default, not only in
MADV_HUGEPAGE regions.

Signed-off-by: default avatarJianguo Wu <wujianguo@huawei.com>
Reviewed-by: default avatarWanpeng Li <liwanp@linux.vnet.ibm.com>
Acked-by: default avatarKirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent c69ded84

mm/huge_memory.c

+6 −5
Original line number Diff line number Diff line
@@ -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

CRA Git | Maintained and supported by SUSTech CRA and CCSE