From: Luiz Capitulino <luizcap@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org, david@kernel.org
Cc: ryan.roberts@arm.com, akpm@linux-foundation.org,
lorenzo.stoakes@oracle.com
Subject: [PATCH 01/11] docs: tmpfs: remove implementation detail reference
Date: Mon, 15 Dec 2025 16:16:43 -0500 [thread overview]
Message-ID: <6c611c5a46548039e714cda6014d47c9d93fcbb2.1765833318.git.luizcap@redhat.com> (raw)
In-Reply-To: <cover.1765833318.git.luizcap@redhat.com>
The tmpfs.rst doc references the has_transparent_hugepage() helper, which
is an implementation detail in the kernel and not relevant for users
wishing to properly configure THP support for tmpfs. Remove it.
Acked-by: David Hildenbrand (Red Hat) <david@kernel.org>
Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
---
Documentation/filesystems/tmpfs.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/tmpfs.rst b/Documentation/filesystems/tmpfs.rst
index d677e0428c3f..46fc986c3388 100644
--- a/Documentation/filesystems/tmpfs.rst
+++ b/Documentation/filesystems/tmpfs.rst
@@ -109,9 +109,8 @@ noswap Disables swap. Remounts must respect the original settings.
====== ===========================================================
tmpfs also supports Transparent Huge Pages which requires a kernel
-configured with CONFIG_TRANSPARENT_HUGEPAGE and with huge supported for
-your system (has_transparent_hugepage(), which is architecture specific).
-The mount options for this are:
+configured with CONFIG_TRANSPARENT_HUGEPAGE and with huge pages
+supported for your system. The mount options for this are:
================ ==============================================================
huge=never Do not allocate huge pages. This is the default.
--
2.52.0
next prev parent reply other threads:[~2025-12-15 21:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 21:16 [PATCH 00/11] mm: thp: always enable mTHP support Luiz Capitulino
2025-12-15 21:16 ` Luiz Capitulino [this message]
2025-12-16 7:40 ` [PATCH 01/11] docs: tmpfs: remove implementation detail reference Baolin Wang
2025-12-15 21:16 ` [PATCH 02/11] mm: introduce pgtable_has_pmd_leaves() Luiz Capitulino
2025-12-15 21:16 ` [PATCH 03/11] drivers: dax: use pgtable_has_pmd_leaves() Luiz Capitulino
2025-12-15 21:16 ` [PATCH 04/11] drivers: i915 selftest: " Luiz Capitulino
2025-12-15 21:16 ` [PATCH 05/11] drivers: nvdimm: " Luiz Capitulino
2025-12-15 21:16 ` [PATCH 06/11] mm: debug_vm_pgtable: " Luiz Capitulino
2025-12-15 21:16 ` [PATCH 07/11] mm: shmem: " Luiz Capitulino
2025-12-16 7:52 ` Baolin Wang
2025-12-16 13:47 ` Luiz Capitulino
2025-12-17 2:03 ` Baolin Wang
2025-12-17 18:50 ` Luiz Capitulino
2025-12-15 21:16 ` [PATCH 08/11] treewide: rename has_transparent_hugepage() to arch_has_pmd_leaves() Luiz Capitulino
2025-12-15 21:16 ` [PATCH 09/11] mm: replace thp_disabled_by_hw() with pgtable_has_pmd_leaves() Luiz Capitulino
2025-12-15 21:16 ` [PATCH 10/11] mm/thp: always enable mTHP support Luiz Capitulino
2025-12-15 21:16 ` [PATCH 11/11] mm/thp: x86: cleanup PSE feature bit usage Luiz Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c611c5a46548039e714cda6014d47c9d93fcbb2.1765833318.git.luizcap@redhat.com \
--to=luizcap@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ryan.roberts@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox