From: Wei Yang <richard.weiyang@gmail.com>
To: Zi Yan <ziy@nvidia.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, david@redhat.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, linux-mm@kvack.org,
wang lian <lianux.mm@gmail.com>
Subject: Re: [Patch v3 4/4] mm/huge_memory: optimize old_order derivation during folio splitting
Date: Fri, 31 Oct 2025 01:50:53 +0000 [thread overview]
Message-ID: <20251031015053.n44qkbtnmwbtpfmv@master> (raw)
In-Reply-To: <9A89CDDB-7C17-4804-8240-E068EA68F7D2@nvidia.com>
On Fri, Oct 24, 2025 at 11:29:00AM -0400, Zi Yan wrote:
>On 24 Oct 2025, at 10:46, Lorenzo Stoakes wrote:
[...]
>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>> index 093b3ffb180f..a4fa8b0e5b5a 100644
>>> --- a/mm/huge_memory.c
>>> +++ b/mm/huge_memory.c
>>> @@ -3596,8 +3596,8 @@ static int __split_unmapped_folio(struct folio *folio, int new_order,
>>> struct address_space *mapping, bool uniform_split)
>>> {
>>> const bool is_anon = folio_test_anon(folio);
>>> - int order = folio_order(folio);
>>> - int start_order = uniform_split ? new_order : order - 1;
>>> + int old_order = folio_order(folio);
>>> + int start_order = uniform_split ? new_order : old_order - 1;
>>> int split_order;
>>>
>>> folio_clear_has_hwpoisoned(folio);
>>> @@ -3609,14 +3609,11 @@ static int __split_unmapped_folio(struct folio *folio, int new_order,
>>> for (split_order = start_order;
>>> split_order >= new_order;
>>
>> A thought for the future - now things are simplified, it might be nice to just
>> separate out the core of this loop and have the uniform split just call the
>> split out function directly, and the non-uniform one do the loop.
>>
>> As it's a bit gross in the uniform case we just let split_order go to new_order
>> - 1 to exit the loop.
>
>Yeah, something like:
>
>if (uniform_split) {
> if (mapping)
> xas_split(xas, folio, old_order);
> split_folio_to_order(...);
> return 0;
>}
>
>for () {
>...
>split_folio_to_order(...);
>...
>}
>
>where split_folio_to_order(...) just
>split memcg, split page owner, pgalloc_tag_split, __split_folio_to_order,
>and stats update
>
This looks reasonable, while I found we already have split_folio_to_order().
>>
>> BUT - let's please save that for another patch :)
>
>I agree.
>>
>> This all looks fine.
>>
>>> split_order--) {
>>> - int old_order = folio_order(folio);
>>> int nr_new_folios = 1UL << (old_order - split_order);
>>>
>>> /* order-1 anonymous folio is not supported */
>>> if (is_anon && split_order == 1)
>>> continue;
>>> - if (uniform_split && split_order != new_order)
>>> - continue;
>>>
>>> if (mapping) {
>>> /*
>>> @@ -3643,7 +3640,13 @@ static int __split_unmapped_folio(struct folio *folio, int new_order,
>>> mod_mthp_stat(old_order, MTHP_STAT_NR_ANON, -1);
>>> mod_mthp_stat(split_order, MTHP_STAT_NR_ANON, nr_new_folios);
>>> }
>>> + /*
>>> + * If uniform split, the process is complete.
>>> + * If non-uniform, continue splitting the folio at @split_at
>>> + * as long as the next @split_order is >= @new_order.
>>> + */
>>> folio = page_folio(split_at);
>>> + old_order = split_order;
>>> }
>>>
>>> return 0;
>>> --
>>> 2.34.1
>>>
>>>
>
>
>--
>Best Regards,
>Yan, Zi
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-10-31 1:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 21:21 [Patch v3 0/4] mm/huge_memory: cleanup __split_unmapped_folio() Wei Yang
2025-10-21 21:21 ` [Patch v3 1/4] mm/huge_memory: avoid reinvoking folio_test_anon() Wei Yang
2025-10-24 14:08 ` Lorenzo Stoakes
2025-10-21 21:21 ` [Patch v3 2/4] mm/huge_memory: update folio stat after successful split Wei Yang
2025-10-22 20:26 ` David Hildenbrand
2025-10-22 20:31 ` Zi Yan
2025-10-23 1:26 ` wang lian
2025-10-24 14:32 ` Lorenzo Stoakes
2025-10-31 0:46 ` Wei Yang
2025-10-21 21:21 ` [Patch v3 3/4] mm/huge_memory: optimize and simplify folio stat update after split Wei Yang
2025-10-22 20:28 ` David Hildenbrand
2025-10-22 20:32 ` Zi Yan
2025-10-23 1:29 ` wang lian
2025-10-24 14:35 ` Lorenzo Stoakes
2025-10-21 21:21 ` [Patch v3 4/4] mm/huge_memory: optimize old_order derivation during folio splitting Wei Yang
2025-10-22 20:29 ` David Hildenbrand
2025-10-22 20:33 ` Zi Yan
2025-10-23 1:32 ` wang lian
2025-10-24 14:46 ` Lorenzo Stoakes
2025-10-24 15:29 ` Zi Yan
2025-10-24 15:33 ` Lorenzo Stoakes
2025-10-31 1:50 ` Wei Yang [this message]
2025-10-31 1:55 ` Zi Yan
2025-10-31 2:00 ` Wei 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=20251031015053.n44qkbtnmwbtpfmv@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=lianux.mm@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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