From: David Hildenbrand <david@redhat.com>
To: Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Muchun Song <muchun.song@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] mm,hugetlb: Allocate frozen pages in alloc_buddy_hugetlb_folio
Date: Fri, 11 Apr 2025 15:44:31 +0200 [thread overview]
Message-ID: <f0373427-b4e8-4612-b668-980d93febe26@redhat.com> (raw)
In-Reply-To: <20250411132359.312708-1-osalvador@suse.de>
On 11.04.25 15:23, Oscar Salvador wrote:
> alloc_buddy_hugetlb_folio() allocates a rmappable folio, then strips the
> rmappable part and freezes it.
> We can simplify all that by allocating frozen pages directly.
>
> Suggested-by: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Oscar Salvador <osalvador@suse.de>
> ---
> mm/hugetlb.c | 17 +----------------
> 1 file changed, 1 insertion(+), 16 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index e3e6ac991b9c..83fa2b9f6fc4 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1950,7 +1950,6 @@ static struct folio *alloc_buddy_hugetlb_folio(struct hstate *h,
> int order = huge_page_order(h);
> struct folio *folio;
> bool alloc_try_hard = true;
> - bool retry = true;
>
> /*
> * By default we always try hard to allocate the folio with
> @@ -1965,22 +1964,8 @@ static struct folio *alloc_buddy_hugetlb_folio(struct hstate *h,
> gfp_mask |= __GFP_RETRY_MAYFAIL;
> if (nid == NUMA_NO_NODE)
> nid = numa_mem_id();
> -retry:
> - folio = __folio_alloc(gfp_mask, order, nid, nmask);
> - /* Ensure hugetlb folio won't have large_rmappable flag set. */
> - if (folio)
> - folio_clear_large_rmappable(folio);
>
> - if (folio && !folio_ref_freeze(folio, 1)) {
> - folio_put(folio);
> - if (retry) { /* retry once */
> - retry = false;
> - goto retry;
> - }
> - /* WOW! twice in a row. */
> - pr_warn("HugeTLB unexpected inflated folio ref count\n");
> - folio = NULL;
> - }
> + folio = (struct folio *)__alloc_frozen_pages(gfp_mask, order, nid, nmask);
>
> /*
> * If we did not specify __GFP_RETRY_MAYFAIL, but still got a
I assume htlb_alloc_mask() will always include _GFP_COMP.
But semantically, it might be wrong: __folio_alloc() will in the memdesc
world also make sure to allocate the memdesc, __alloc_frozen_pages() not.
Maybe one would want a __alloc_frozen_folio() .... @willy?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-11 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 13:23 Oscar Salvador
2025-04-11 13:32 ` Vlastimil Babka
2025-04-11 13:44 ` David Hildenbrand [this message]
2025-04-11 14:21 ` Matthew Wilcox
2025-04-11 17:13 ` David Hildenbrand
2025-04-13 18:50 ` Oscar Salvador
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=f0373427-b4e8-4612-b668-980d93febe26@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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