From: kexinsun <kexinsun@smail.nju.edu.cn>
To: muchun.song@linux.dev
Cc: osalvador@suse.de, david@kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
julia.lawall@inria.fr, xutong.ma@inria.fr, yunbolyu@smu.edu.sg,
ratnadiraw@smu.edu.sg, kexinsun@smail.nju.edu.cn
Subject: [PATCH] mm/hugetlb_vmemmap: update outdated comment
Date: Tue, 24 Feb 2026 10:28:40 +0800 [thread overview]
Message-ID: <20260224022840.1936-1-kexinsun@smail.nju.edu.cn> (raw)
The function vmemmap_pte_range() was refactored into vmemmap_pte_entry()
by commit fb93ed63345f ("mm: hugetlb_vmemmap: use walk_page_range_novma()
to simplify the code"). Both functions share the key behavior that the
reuse page is identified first before remapping begins. Update the
comment accordingly.
Signed-off-by: kexinsun <kexinsun@smail.nju.edu.cn>
---
mm/hugetlb_vmemmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/hugetlb_vmemmap.c b/mm/hugetlb_vmemmap.c
index a9280259e12a..5156e4038b5f 100644
--- a/mm/hugetlb_vmemmap.c
+++ b/mm/hugetlb_vmemmap.c
@@ -350,7 +350,7 @@ static int vmemmap_remap_free(unsigned long start, unsigned long end,
/*
* In order to make remapping routine most efficient for the huge pages,
* the routine of vmemmap page table walking has the following rules
- * (see more details from the vmemmap_pte_range()):
+ * (see more details from the vmemmap_pte_entry()):
*
* - The range [@start, @end) and the range [@reuse, @reuse + PAGE_SIZE)
* should be continuous.
--
2.25.1
next reply other threads:[~2026-02-24 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 2:28 kexinsun [this message]
2026-02-24 5:03 ` Muchun Song
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=20260224022840.1936-1-kexinsun@smail.nju.edu.cn \
--to=kexinsun@smail.nju.edu.cn \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=ratnadiraw@smu.edu.sg \
--cc=xutong.ma@inria.fr \
--cc=yunbolyu@smu.edu.sg \
/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