mm/thp: fix stale comments of transparent_hugepage_flags
Subsystems (2)
PATCH RESEND v2 1/1 mm/thp: fix stale comments of transparent_hugepage_flags
Changelog:
*v1 -> v2: also update the stale comments about default transparent
hugepage support pointed by Wanpeng Li.
Since commit 13ece886d9(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 d39d33c332(thp: enable direct defrag), defrag is enable for all transparent hugepage page faults by default, not only in MADV_HUGEPAGE regions.
--- mm/huge_memory.c | 11 ++++++----- 1 files changed, 6 insertions(+), 5 deletions(-)
mm/huge_memory.c +6 -5
@@ -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
Signature · 8 lines
1.7.1 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 4 lines · Jianguo Wu
Changelog:
*v1 -> v2: also update the stale comments about default transparent hugepage support pointed by Wanpeng Li.
Quoted 8 lines
Since commit 13ece886d9(thp: transparent hugepage config choice), transparent hugepage support is disabled by default, and
TRANSPARENT_HUGEPAGE_ALWAYSis configured when TRANSPARENT_HUGEPAGE=y.And since commit d39d33c332(thp: enable direct defrag), defrag is enable for all transparent hugepage page faults by default, not only in
MADV_HUGEPAGEregions.
Quoted 25 lines
Signed-off-by Jianguo Wu <[email protected]>---
mm/huge_memory.c| 11 ++++++-----1 files changed, 6 insertions(+), 5 deletions(-)mm/huge_memory.c +6
-5@@ -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. */
Quoted 5 lines
unsigned long
transparent_hugepage_flags__read_mostly= #ifdefCONFIG_TRANSPARENT_HUGEPAGE_ALWAYSSignature · 1 line
1.7.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 4 lines · Jianguo Wu
Changelog:
*v1 -> v2: also update the stale comments about default transparent hugepage support pointed by Wanpeng Li.
Quoted 8 lines
Since commit 13ece886d9(thp: transparent hugepage config choice), transparent hugepage support is disabled by default, and
TRANSPARENT_HUGEPAGE_ALWAYSis configured when TRANSPARENT_HUGEPAGE=y.And since commit d39d33c332(thp: enable direct defrag), defrag is enable for all transparent hugepage page faults by default, not only in
MADV_HUGEPAGEregions.
Quoted 25 lines
Signed-off-by Jianguo Wu <[email protected]>---
mm/huge_memory.c| 11 ++++++-----1 files changed, 6 insertions(+), 5 deletions(-)mm/huge_memory.c +6
-5@@ -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. */
Quoted 5 lines
unsigned long
transparent_hugepage_flags__read_mostly= #ifdefCONFIG_TRANSPARENT_HUGEPAGE_ALWAYSSignature · 1 line
1.7.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 8 lines · Jianguo Wu
Changelog:
*v1 -> v2: also update the stale comments about default transparent
hugepage support pointed by Wanpeng Li.Since commit 13ece886d9(thp: transparent hugepage config choice), transparent hugepage support is disabled by default, and
TRANSPARENT_HUGEPAGE_ALWAYSis configured when TRANSPARENT_HUGEPAGE=y.
Quoted 5 lines
And since commit d39d33c332(thp: enable direct defrag), defrag is enable for all transparent hugepage page faults by default, not only in
MADV_HUGEPAGEregions.Signed-off-by Jianguo Wu <[email protected]>
Signature · 7 lines
Kirill A. Shutemov -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>