From: Qi Zheng <qi.zheng@linux.dev>
To: Muchun Song <songmuchun@bytedance.com>,
Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>
Cc: Lance Yang <lance.yang@linux.dev>,
James Houghton <jthoughton@google.com>,
David Hildenbrand <david@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/12] mm: hugetlb_vmemmap: simplify vmemmap head page handling
Date: Sun, 1 Nov 2026 14:31:33 +0800 [thread overview]
Message-ID: <587556c5-389f-4616-99f9-f0216b72f112@linux.dev> (raw)
In-Reply-To: <20261020115824.823278-2-songmuchun@bytedance.com>
On 10/20/26 7:58 PM, Muchun Song wrote:
> The new head page is already tracked on the vmemmap page list before
> remapping starts. Passing it separately gives the remap walker two
> ways to refer to the same page and unnecessarily complicates its
> interface.
>
> Use the page list as the single handoff mechanism for the head page,
> removing the redundant state from the walker.
>
> No functional change intended.
>
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> ---
> mm/hugetlb_vmemmap.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/mm/hugetlb_vmemmap.c b/mm/hugetlb_vmemmap.c
> index 8b3abb562599..164e93e980bf 100644
> --- a/mm/hugetlb_vmemmap.c
> +++ b/mm/hugetlb_vmemmap.c
> @@ -25,7 +25,6 @@
> *
> * @remap_pte: called for each lowest-level entry (PTE).
> * @nr_walked: the number of walked pte.
> - * @vmemmap_head: the page to be installed as first in the vmemmap range
> * @vmemmap_tail: the page to be installed as non-first in the vmemmap range
> * @vmemmap_pages: the list head of the vmemmap pages that can be freed
> * or is mapped from.
The @vmemmap_pages description may need updating as well. After this
change, the list is no longer only an output list for pages to be freed;
its first entry is also consumed as the new head backing page. It would
be helpful to document this input contract explicitly.
Other than that, once Lance's comment is addressed:
Reviewed-by: Qi Zheng <qi.zheng@linux.dev>
Thanks,
Qi
> @@ -37,7 +36,6 @@ struct vmemmap_remap_walk {
> struct vmemmap_remap_walk *walk);
>
> unsigned long nr_walked;
> - struct page *vmemmap_head;
> struct page *vmemmap_tail;
> struct list_head *vmemmap_pages;
>
> @@ -208,10 +206,13 @@ static void vmemmap_remap_pte(pte_t *pte, unsigned long addr,
> pte_t entry;
>
> /* Remapping the head page requires r/w */
> - if (unlikely(walk->nr_walked == 0 && walk->vmemmap_head)) {
> + if (unlikely(walk->nr_walked == 0)) {
> + struct page *head;
> +
> VM_WARN_ON_ONCE(!PageHead((const struct page *)addr));
>
> - list_del(&walk->vmemmap_head->lru);
> + head = list_first_entry(walk->vmemmap_pages, struct page, lru);
> + list_del(&head->lru);
>
> /*
> * Makes sure that preceding stores to the page contents from
> @@ -220,7 +221,7 @@ static void vmemmap_remap_pte(pte_t *pte, unsigned long addr,
> */
> smp_wmb();
>
> - entry = mk_pte(walk->vmemmap_head, PAGE_KERNEL);
> + entry = mk_pte(head, PAGE_KERNEL);
> } else {
> VM_WARN_ON_ONCE(!PageTail((const struct page *)addr));
>
> @@ -289,7 +290,6 @@ static int vmemmap_remap_split(unsigned long start, unsigned long end)
> * to remap.
> * @end: end address of the vmemmap virtual address range that we want to
> * remap.
> - * @vmemmap_head: the page to be installed as first in the vmemmap range
> * @vmemmap_tail: the page to be installed as non-first in the vmemmap range
> * @vmemmap_pages: list to deposit vmemmap pages to be freed. It is callers
> * responsibility to free pages.
> @@ -298,7 +298,6 @@ static int vmemmap_remap_split(unsigned long start, unsigned long end)
> * Return: %0 on success, negative error code otherwise.
> */
> static int vmemmap_remap_free(unsigned long start, unsigned long end,
> - struct page *vmemmap_head,
> struct page *vmemmap_tail,
> struct list_head *vmemmap_pages,
> unsigned long flags)
> @@ -306,7 +305,6 @@ static int vmemmap_remap_free(unsigned long start, unsigned long end,
> int ret;
> struct vmemmap_remap_walk walk = {
> .remap_pte = vmemmap_remap_pte,
> - .vmemmap_head = vmemmap_head,
> .vmemmap_tail = vmemmap_tail,
> .vmemmap_pages = vmemmap_pages,
> .flags = flags,
> @@ -547,8 +545,7 @@ static int __hugetlb_vmemmap_optimize_folio(const struct hstate *h,
> * they can be freed by the caller.
> */
> ret = vmemmap_remap_free(vmemmap_start, vmemmap_end,
> - vmemmap_head, vmemmap_tail,
> - vmemmap_pages, flags);
> + vmemmap_tail, vmemmap_pages, flags);
> out:
> if (ret)
> folio_clear_hugetlb_vmemmap_optimized(folio);
next prev parent reply other threads:[~2026-11-01 6:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 11:52 [PATCH 00/12] mm: Decouple folio-based vmemmap optimization from HugeTLB Muchun Song
2026-10-20 11:52 ` [PATCH 01/12] mm: hugetlb_vmemmap: remove HugeTLB-specific vmemmap optimization macros Muchun Song
2026-10-22 3:43 ` Lance Yang
2026-10-31 8:03 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 02/12] mm: hugetlb_vmemmap: unify VMEMMAP_{SPLIT,REMAP}_NO_TLB_FLUSH Muchun Song
2026-10-20 11:58 ` [PATCH 03/12] mm: hugetlb_vmemmap: simplify vmemmap head page handling Muchun Song
2026-10-22 6:24 ` Lance Yang
2026-10-22 6:27 ` Muchun Song
2026-10-22 7:23 ` Lance Yang
2026-11-01 6:31 ` Qi Zheng [this message]
2026-11-01 6:42 ` Muchun Song
2026-10-20 11:58 ` [PATCH 04/12] mm: hugetlb_vmemmap: generalize vmemmap page allocation Muchun Song
2026-10-22 13:54 ` Lance Yang
2026-11-01 6:39 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 05/12] mm: hugetlb_vmemmap: unify writable vmemmap page preparation Muchun Song
2026-10-22 14:13 ` Lance Yang
2026-11-01 6:51 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 06/12] mm: hugetlb_vmemmap: rename vmemmap_remap_pte() to vmemmap_optimize_pte() Muchun Song
2026-10-23 0:55 ` Lance Yang
2026-11-01 6:52 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 07/12] mm: hugetlb_vmemmap: simplify shared tail page handling Muchun Song
2026-10-23 2:20 ` Lance Yang
2026-10-23 2:32 ` Muchun Song
2026-11-01 7:03 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 08/12] mm: hugetlb_vmemmap: move alloc_vmemmap_page_list() next to its free helper Muchun Song
2026-10-23 2:47 ` Lance Yang
2026-11-01 7:03 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 09/12] mm: hugetlb_vmemmap: make vmemmap optimization folio-oriented Muchun Song
2026-10-23 3:39 ` Lance Yang
2026-11-01 7:08 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 10/12] mm: hugetlb_vmemmap: make vmemmap restoration folio-oriented Muchun Song
2026-10-23 3:46 ` Lance Yang
2026-10-23 3:58 ` Muchun Song
2026-11-01 7:14 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 11/12] mm: hugetlb_vmemmap: unify vmemmap range restoration Muchun Song
2026-10-23 3:53 ` Lance Yang
2026-11-01 7:16 ` Qi Zheng
2026-10-20 11:58 ` [PATCH 12/12] mm: hugetlb_vmemmap: make vmemmap PTE conversion folio-oriented Muchun Song
2026-10-23 7:33 ` Lance Yang
2026-11-01 7:18 ` Qi Zheng
2026-10-22 3:52 ` [PATCH 02/12] mm: hugetlb_vmemmap: unify VMEMMAP_{SPLIT,REMAP}_NO_TLB_FLUSH Lance Yang
2026-11-01 6:22 ` Qi Zheng
2026-11-01 6:56 ` Muchun Song
2026-11-01 6:59 ` Qi Zheng
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=587556c5-389f-4616-99f9-f0216b72f112@linux.dev \
--to=qi.zheng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jthoughton@google.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.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
all inboxes | Powered by JetHome®