From: Mike Kravetz <mike.kravetz@oracle.com>
To: Yuan Can <yuancan@huawei.com>
Cc: muchun.song@linux.dev, akpm@linux-foundation.org,
linux-mm@kvack.org, wangkefeng.wang@huawei.com
Subject: Re: [PATCH] mm: hugetlb_vmemmap: allow alloc vmemmap pages fallback to other nodes
Date: Thu, 7 Sep 2023 13:31:44 -0700 [thread overview]
Message-ID: <20230907203144.GG3640@monkey> (raw)
In-Reply-To: <20230906093157.9737-1-yuancan@huawei.com>
On 09/06/23 17:31, Yuan Can wrote:
> In vmemmap_remap_free(), a new head vmemmap page is allocated to avoid
> breaking a contiguous block of struct page memory, however, the allocation
> can always fail when the given node is movable node. Remove the
> __GFP_THISNODE to help avoid fragmentation.
>
> Suggested-by: Mike Kravetz <mike.kravetz@oracle.com>
> Suggested-by: Muchun Song <songmuchun@bytedance.com>
> Signed-off-by: Yuan Can <yuancan@huawei.com>
> ---
> mm/hugetlb_vmemmap.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Thanks,
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
--
Mike Kravetz
>
> diff --git a/mm/hugetlb_vmemmap.c b/mm/hugetlb_vmemmap.c
> index c2007ef5e9b0..27fc65b8e37e 100644
> --- a/mm/hugetlb_vmemmap.c
> +++ b/mm/hugetlb_vmemmap.c
> @@ -325,8 +325,7 @@ static int vmemmap_remap_free(unsigned long start, unsigned long end,
> .vmemmap_pages = &vmemmap_pages,
> };
> int nid = page_to_nid((struct page *)start);
> - gfp_t gfp_mask = GFP_KERNEL | __GFP_THISNODE | __GFP_NORETRY |
> - __GFP_NOWARN;
> + gfp_t gfp_mask = GFP_KERNEL | __GFP_NORETRY | __GFP_NOWARN;
>
> /*
> * Allocate a new head vmemmap page to avoid breaking a contiguous
> --
> 2.17.1
>
prev parent reply other threads:[~2023-09-07 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:31 Yuan Can
2023-09-07 6:37 ` Muchun Song
2023-09-07 20:31 ` Mike Kravetz [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=20230907203144.GG3640@monkey \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=wangkefeng.wang@huawei.com \
--cc=yuancan@huawei.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