From: Enze Li <lienze@kylinos.cn>
To: muchun.song@linux.dev, osalvador@suse.de, david@kernel.org,
akpm@linux-foundation.org, corbet@lwn.net
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
Enze Li <lienze@kylinos.cn>
Subject: [PATCH] docs: hugetlbpage.rst: clarify HugePages_Total in hugetlbpage.rst
Date: Fri, 23 Oct 2026 18:08:59 +0800 [thread overview]
Message-ID: <20261023100859.70744-1-lienze@kylinos.cn> (raw)
"the size of the pool of huge pages" confused me, since it sounds
like a size in bytes. It's actually the number of persistent huge
pages of the default size, and pools of other sizes aren't shown
here at all. Reword it and point to /sys/kernel/mm/hugepages for
those.
Signed-off-by: Enze Li <lienze@kylinos.cn>
---
Documentation/admin-guide/mm/hugetlbpage.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/mm/hugetlbpage.rst b/Documentation/admin-guide/mm/hugetlbpage.rst
index 2075f1f14a42..01fa9f61c9a9 100644
--- a/Documentation/admin-guide/mm/hugetlbpage.rst
+++ b/Documentation/admin-guide/mm/hugetlbpage.rst
@@ -43,7 +43,9 @@ The output of ``cat /proc/meminfo`` will include lines like::
where:
HugePages_Total
- is the size of the pool of huge pages.
+ is the number of persistent huge pages of the default size
+ in the pool. Pools of other huge page sizes are not shown
+ here; see ``/sys/kernel/mm/hugepages`` described below.
HugePages_Free
is the number of huge pages in the pool that are not yet
allocated.
base-commit: 3fdcce698abd9193752ee89fb1a440cdceb1b74a
--
2.56.0
next reply other threads:[~2026-10-23 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 10:08 Enze Li [this message]
2026-10-25 13:25 ` [PATCH] docs: hugetlbpage.rst: clarify HugePages_Total in hugetlbpage.rst Daniel Pereira
[not found] ` <1792998249167036.77.seg@mailgw.kylinos.cn>
2026-10-26 7:47 ` Enze Li
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=20261023100859.70744-1-lienze@kylinos.cn \
--to=lienze@kylinos.cn \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
/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