linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: yangge1116@126.com
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, 21cnbao@gmail.com,
	david@redhat.com, baolin.wang@linux.alibaba.com,
	osalvador@suse.de, liuzixing@hygon.cn,
	Ge Yang <yangge1116@126.com>
Subject: Re: [PATCH V2] mm/hugetlb: wait for hugepage folios to be freed
Date: Tue, 18 Feb 2025 14:52:54 +0800	[thread overview]
Message-ID: <574F9D6A-F370-4A8C-9044-BC0A6189F055@linux.dev> (raw)
In-Reply-To: <1739604026-2258-1-git-send-email-yangge1116@126.com>

[-- Attachment #1: Type: text/plain, Size: 5165 bytes --]



> On Feb 15, 2025, at 15:20, yangge1116@126.com wrote:
> 
> From: Ge Yang <yangge1116@126.com>
> 
> Since the introduction of commit b65d4adbc0f0 ("mm: hugetlb: defer freeing
> of HugeTLB pages"), which supports deferring the freeing of HugeTLB pages,
> the allocation of contiguous memory through cma_alloc() may fail
> probabilistically.
> 
> In the CMA allocation process, if it is found that the CMA area is occupied
> by in-use hugepage folios, these in-use hugepage folios need to be migrated
> to another location. When there are no available hugepage folios in the
> free HugeTLB pool during the migration of in-use HugeTLB pages, new folios
> are allocated from the buddy system. A temporary state is set on the newly
> allocated folio. Upon completion of the hugepage folio migration, the
> temporary state is transferred from the new folios to the old folios.
> Normally, when the old folios with the temporary state are freed, it is
> directly released back to the buddy system. However, due to the deferred
> freeing of HugeTLB pages, the PageBuddy() check fails, ultimately leading
> to the failure of cma_alloc().
> 
> Here is a simplified call trace illustrating the process:
> cma_alloc()
>    ->__alloc_contig_migrate_range() // Migrate in-use hugepage
>        ->unmap_and_move_huge_page()
>            ->folio_putback_hugetlb() // Free old folios
>    ->test_pages_isolated()
>        ->__test_page_isolated_in_pageblock()
>             ->PageBuddy(page) // Check if the page is in buddy
> 
> To resolve this issue, we have implemented a function named
> wait_for_hugepage_folios_freed(). This function ensures that the hugepage
> folios are properly released back to the buddy system after their migration
> is completed. By invoking wait_for_hugepage_folios_freed() before calling
> PageBuddy(), we ensure that PageBuddy() will succeed.
> 
> Fixes: b65d4adbc0f0 ("mm: hugetlb: defer freeing of HugeTLB pages")
> Signed-off-by: Ge Yang <yangge1116@126.com>
> ---
> 
> V2:
> - flush all folios at once suggested by David
> 
> include/linux/hugetlb.h |  5 +++++
> mm/hugetlb.c            |  8 ++++++++
> mm/page_isolation.c     | 10 ++++++++++
> 3 files changed, 23 insertions(+)
> 
> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
> index 6c6546b..04708b0 100644
> --- a/include/linux/hugetlb.h
> +++ b/include/linux/hugetlb.h
> @@ -697,6 +697,7 @@ bool hugetlb_bootmem_page_zones_valid(int nid, struct huge_bootmem_page *m);
> 
> int isolate_or_dissolve_huge_page(struct page *page, struct list_head *list);
> int replace_free_hugepage_folios(unsigned long start_pfn, unsigned long end_pfn);
> +void wait_for_hugepage_folios_freed(void);
> struct folio *alloc_hugetlb_folio(struct vm_area_struct *vma,
>                unsigned long addr, bool cow_from_owner);
> struct folio *alloc_hugetlb_folio_nodemask(struct hstate *h, int preferred_nid,
> @@ -1092,6 +1093,10 @@ static inline int replace_free_hugepage_folios(unsigned long start_pfn,
>    return 0;
> }
> 
> +static inline void wait_for_hugepage_folios_freed(void)
> +{
> +}
> +
> static inline struct folio *alloc_hugetlb_folio(struct vm_area_struct *vma,
>                       unsigned long addr,
>                       bool cow_from_owner)
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 30bc34d..36dd3e4 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2955,6 +2955,14 @@ int replace_free_hugepage_folios(unsigned long start_pfn, unsigned long end_pfn)
>    return ret;
> }
> 
> +void wait_for_hugepage_folios_freed(void)

We usually use the "hugetlb" term now instead of "huge_page" to differentiate with THP. So I suggest naming it as wait_for_hugetlb_folios_freed().

> +{
> +    struct hstate *h;
> +
> +    for_each_hstate(h)
> +        flush_free_hpage_work(h);

Because all hstate use the shared work to defer the freeing of hugetlb pages, we only need to flush once. Directly useing flush_work(&free_hpage_work) is enough.

> +}
> +
> typedef enum {
>    /*
>     * For either 0/1: we checked the per-vma resv map, and one resv
> diff --git a/mm/page_isolation.c b/mm/page_isolation.c
> index 8ed53ee0..f56cf02 100644
> --- a/mm/page_isolation.c
> +++ b/mm/page_isolation.c
> @@ -615,6 +615,16 @@ int test_pages_isolated(unsigned long start_pfn, unsigned long end_pfn,
>    int ret;
> 
>    /*
> +     * Due to the deferred freeing of HugeTLB folios, the hugepage folios may
> +     * not immediately release to the buddy system. This can cause PageBuddy()
> +     * to fail in __test_page_isolated_in_pageblock(). To ensure that the
> +     * hugepage folios are properly released back to the buddy system, we

hugetlb folios, pls.

Thanks,
Muchun

> +     * invoke the wait_for_hugepage_folios_freed() function to wait for the
> +     * release to complete.
> +     */
> +    wait_for_hugepage_folios_freed();
> +
> +    /*
>     * Note: pageblock_nr_pages != MAX_PAGE_ORDER. Then, chunks of free
>     * pages are not aligned to pageblock_nr_pages.
>     * Then we just check migratetype first.
> -- 
> 2.7.4
> 

[-- Attachment #2: Type: text/html, Size: 8750 bytes --]

  parent reply	other threads:[~2025-02-18  6:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15  7:20 yangge1116
2025-02-18  4:34 ` Andrew Morton
2025-02-18  7:24   ` Ge Yang
2025-02-18  6:52 ` Muchun Song [this message]
2025-02-18  8:52   ` David Hildenbrand
2025-02-18  9:06     ` Ge Yang
2025-02-18  7:05 ` Muchun Song
2025-02-18  7:25   ` Ge Yang

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=574F9D6A-F370-4A8C-9044-BC0A6189F055@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuzixing@hygon.cn \
    --cc=osalvador@suse.de \
    --cc=yangge1116@126.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