transhuge.rst claims seven policies for transparent_hugepage_shmem= and four for transparent_hugepage_tmpfs=. Both boot parameters are parsed by shmem_parse_huge(), which accepts six: always, within_size, advise, never, deny and force. The "four" applies only to the per-mount huge= option (shmem_param_enums_huge). Fix both counts to six. Signed-off-by: Song Hu --- Documentation/admin-guide/mm/transhuge.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/admin-guide/mm/transhuge.rst b/Documentation/admin-guide/mm/transhuge.rst index b187d618452f..72e944f49da5 100644 --- a/Documentation/admin-guide/mm/transhuge.rst +++ b/Documentation/admin-guide/mm/transhuge.rst @@ -389,14 +389,14 @@ is not defined within a valid ``thp_anon``, its policy will default to Similarly to ``transparent_hugepage``, you can control the hugepage allocation policy for the internal shmem mount by using the kernel parameter ``transparent_hugepage_shmem=``, where ```` is one of the -seven valid policies for shmem (``always``, ``within_size``, ``advise``, +six valid policies for shmem (``always``, ``within_size``, ``advise``, ``never``, ``deny``, and ``force``). Similarly to ``transparent_hugepage_shmem``, you can control the default hugepage allocation policy for the tmpfs mount by using the kernel parameter ``transparent_hugepage_tmpfs=``, where ```` is one of the -four valid policies for tmpfs (``always``, ``within_size``, ``advise``, -``never``). The tmpfs mount default policy is ``never``. +six valid policies for tmpfs (``always``, ``within_size``, ``advise``, +``never``, ``deny``, and ``force``). The tmpfs mount default policy is ``never``. Additionally, Kconfig options are available to set the default hugepage policies for shmem (``CONFIG_TRANSPARENT_HUGEPAGE_SHMEM_HUGE_*``) and tmpfs -- 2.43.0