linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Oscar Salvador <osalvador@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Muchun Song <muchun.song@linux.dev>,
	David Hildenbrand <david@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm, hugetlb: Avoid passing a null nodemask when there is mbind policy
Date: Wed, 16 Apr 2025 09:08:29 +0200	[thread overview]
Message-ID: <9f5c4c8e-bdb4-433a-8d1b-855cbebfe88d@suse.cz> (raw)
In-Reply-To: <20250415121503.376811-1-osalvador@suse.de>

On 4/15/25 14:15, Oscar Salvador wrote:
> Before trying to allocate a page, gather_surplus_pages() sets up a nodemask
> for the nodes we can allocate from, but instead of passing the nodemask
> down the road to the page allocator, it iterates over the nodes within that
> nodemask right there, meaning that the page allocator will receive a preferred_nid
> and a null nodemask.
> 
> This is a problem when using a memory policy, because it might be that
> the page allocator ends up using a node as a fallback which is not
> represented in the policy.
> 
> Avoid that by passing the nodemask directly to the page allocator, so it can
> filter out fallback nodes that are not part of the nodemask.

It will also try the fallbacks using numa distance and not incrementing nid.

> Signed-off-by: Oscar Salvador <osalvador@suse.de>

Reviewed-by: Vlastimil Babka <vbabka@suse.cz>

> ---
>  mm/hugetlb.c | 22 ++++++----------------
>  1 file changed, 6 insertions(+), 16 deletions(-)
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index ccc4f08f8481..5e1cba0f835f 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2419,7 +2419,6 @@ static int gather_surplus_pages(struct hstate *h, long delta)
>  	long i;
>  	long needed, allocated;
>  	bool alloc_ok = true;
> -	int node;
>  	nodemask_t *mbind_nodemask, alloc_nodemask;
>  
>  	mbind_nodemask = policy_mbind_nodemask(htlb_alloc_mask(h));
> @@ -2443,21 +2442,12 @@ static int gather_surplus_pages(struct hstate *h, long delta)
>  	for (i = 0; i < needed; i++) {
>  		folio = NULL;
>  
> -		/* Prioritize current node */
> -		if (node_isset(numa_mem_id(), alloc_nodemask))
> -			folio = alloc_surplus_hugetlb_folio(h, htlb_alloc_mask(h),
> -					numa_mem_id(), NULL);
> -
> -		if (!folio) {
> -			for_each_node_mask(node, alloc_nodemask) {
> -				if (node == numa_mem_id())
> -					continue;
> -				folio = alloc_surplus_hugetlb_folio(h, htlb_alloc_mask(h),
> -						node, NULL);
> -				if (folio)
> -					break;
> -			}
> -		}
> +		/*
> +		 * It is okay to use NUMA_NO_NODE because we use numa_mem_id()
> +		 * down the road to pick the current node if that is the case.
> +		 */
> +		folio = alloc_surplus_hugetlb_folio(h, htlb_alloc_mask(h),
> +						    NUMA_NO_NODE, &alloc_nodemask);
>  		if (!folio) {
>  			alloc_ok = false;
>  			break;



      reply	other threads:[~2025-04-16  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 12:15 Oscar Salvador
2025-04-16  7:08 ` Vlastimil Babka [this message]

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=9f5c4c8e-bdb4-433a-8d1b-855cbebfe88d@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@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