From: Ge Yang <yangge1116@126.com>
To: SeongJae Park <sj@kernel.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
21cnbao@gmail.com, david@redhat.com,
baolin.wang@linux.alibaba.com, muchun.song@linux.dev,
liuzixing@hygon.cn
Subject: Re: [PATCH] replace free hugepage folios after migration
Date: Fri, 20 Dec 2024 17:03:28 +0800 [thread overview]
Message-ID: <1c05db02-f1f7-475b-ad89-9c00ab970604@126.com> (raw)
In-Reply-To: <20241219184301.63011-1-sj@kernel.org>
在 2024/12/20 2:43, SeongJae Park 写道:
> Hello,
>
> On Wed, 18 Dec 2024 14:33:08 +0800 yangge1116@126.com wrote:
>
> [...]
>> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
>> index ae4fe86..7d36ac8 100644
>> --- a/include/linux/hugetlb.h
>> +++ b/include/linux/hugetlb.h
>> @@ -681,6 +681,7 @@ struct huge_bootmem_page {
>> };
>>
>> 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);
>> struct folio *alloc_hugetlb_folio(struct vm_area_struct *vma,
>> unsigned long addr, int avoid_reserve);
>> struct folio *alloc_hugetlb_folio_nodemask(struct hstate *h, int preferred_nid,
>> @@ -1059,6 +1060,11 @@ static inline int isolate_or_dissolve_huge_page(struct page *page,
>> return -ENOMEM;
>> }
>>
>> +int replace_free_hugepage_folios(unsigned long start_pfn, unsigned long end_pfn)
>> +{
>> + return 0;
>> +}
>> +
>
> I think this should be static inline. Otherwise, build fails when
> CONFIG_HUGETLB_PAGE is unset. Since this is already merged into mm-unstable
> and the problem and fix seems straigthforward, I directly sent my fix:
> https://lore.kernel.org/20241219183753.62922-1-sj@kernel.org
>
>
> Thanks,
> SJ
>
> [...]
Thanks.
next prev parent reply other threads:[~2024-12-20 9:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 6:33 yangge1116
2024-12-19 16:40 ` David Hildenbrand
2024-12-20 8:56 ` Ge Yang
2024-12-20 16:30 ` David Hildenbrand
2024-12-21 12:04 ` Ge Yang
2024-12-21 14:32 ` David Hildenbrand
2024-12-22 11:50 ` Ge Yang
2024-12-19 18:43 ` SeongJae Park
2024-12-20 9:03 ` Ge Yang [this message]
2024-12-21 14:35 ` David Hildenbrand
2024-12-22 8:13 ` Ge Yang
2025-01-08 21:05 ` David Hildenbrand
2025-01-09 9:50 ` 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=1c05db02-f1f7-475b-ad89-9c00ab970604@126.com \
--to=yangge1116@126.com \
--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=muchun.song@linux.dev \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.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