From: Yuan Can <yuancan@huawei.com>
To: Muchun Song <muchun.song@linux.dev>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH] mm: hugetlb_vmemmap: avoid allocation failure message in alloc_vmemmap_page_list()
Date: Wed, 6 Sep 2023 15:29:31 +0800 [thread overview]
Message-ID: <1ac09088-6309-1bb5-5c8f-18eaaedeaf23@huawei.com> (raw)
In-Reply-To: <F157C83D-16BC-43E2-B094-CEA416D2F49D@linux.dev>
在 2023/9/6 15:25, Muchun Song 写道:
>
>> On Sep 6, 2023, at 15:22, Yuan Can <yuancan@huawei.com> wrote:
>>
>>
>> 在 2023/9/6 14:52, Muchun Song 写道:
>>>
>>>> On Sep 6, 2023, at 14:34, Yuan Can <yuancan@huawei.com> wrote:
>>>>
>>>> When vmemmap pages allocation failed, the hugetlb pages fail to free,
>>>> which is not an fatel error, so avoid the allocation failure report by
>>>> passing __GFP_NOWARN in gfp_mask.
>>>>
>>> You have misunderstand me and Mike. We mean the memory allocation
>>> in vmemmap_remap_free() which also use __GFP_THISNODE, it has the
>>> same issue as you fixed in another thread. But the failure of memory
>>> allocation is not fetal. And it is better to remove __GFP_THISNODE
>>> as well.
>>>
>>> Thanks.
>>>
>> Ok, sorry about this, I will send another patch to remove __GFP_THISNODE in
>> vmemmap_remap_free, and I would like to know is it ok to add __GFP_NOWARN in
>> alloc_vmemmap_page_list()?
> Do not do this. We need a warning here.
>
> Thanks.
Ok, thanks for the reply.
--
Best regards,
Yuan Can
prev parent reply other threads:[~2023-09-06 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 6:34 Yuan Can
2023-09-06 6:52 ` Muchun Song
2023-09-06 7:22 ` Yuan Can
2023-09-06 7:25 ` Muchun Song
2023-09-06 7:29 ` Yuan Can [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=1ac09088-6309-1bb5-5c8f-18eaaedeaf23@huawei.com \
--to=yuancan@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=wangkefeng.wang@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