All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: David Hildenbrand <david@redhat.com>
Cc: Liam.Howlett@oracle.com, baohua@kernel.org,
	baolin.wang@linux.alibaba.com, dev.jain@arm.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lorenzo.stoakes@oracle.com, npache@redhat.com,
	ryan.roberts@arm.com, usamaarif642@gmail.com, ziy@nvidia.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH 1/1] mm: avoid processing mlocked THPs in deferred split shrinker
Date: Mon, 8 Sep 2025 16:13:22 +0800	[thread overview]
Message-ID: <bc1182e7-3f70-4645-b8c4-a97898e57041@linux.dev> (raw)
In-Reply-To: <5a1429ad-3900-404a-bdca-f25623ce603a@redhat.com>



On 2025/9/8 15:38, David Hildenbrand wrote:
> On 08.09.25 06:07, Lance Yang wrote:
>> From: Lance Yang <lance.yang@linux.dev>
> 
> Subject should likely be more specific:
> 
> mm: skip mlocked THPs that are underused early in deferred_split_scan()

Right, that's a much better and more precise subject. Thanks!

> 
>>
>> When a new THP is faulted in or collapsed, it is unconditionally added to
>> the deferred split queue. If this THP is subsequently mlocked, it remains
>> on the queue but is removed from the LRU and marked unevictable.
>>
>> During memory reclaim, deferred_split_scan() will still pick up this 
>> large
>> folio. Because it's not partially mapped, it will proceed to call
>> thp_underused() and then attempt to split_folio() to free all zero-filled
>> subpages.
>>
>> This is a pointless waste of CPU cycles. The folio is mlocked and
>> unevictable, so any attempt to reclaim memory from it via splitting is
>> doomed to fail.
> 
> I think the whole description is a bit misleading: we're not reclaiming
> memory from fully-mapped THPs even when they are underused, because it
> could violate mlock() semantics where we don't want a page fault+memory 
> allocation on next access.
> 
> So something like the following might be clearer.
> 
> "When we stumble over a fully-mapped THP in the deferred shrinker, it 
> does not make sense trying to detect whether it is underused, because 
> try_to_map_unused_to_zeropage(), called while splitting the folio, will 
> not actually replace any zero-ed pages by the shared zeropage.
> 
> Splitting the folio in that case does not make any sense, so let's not 
> even scan if the folio is underused.
> "

Nice, that makes it much clearer. My understanding was indeed imprecise.

> 
> 
> 
> If I run my reproducer from [1] and mlock() the pages just after 
> allocating them, then I essentially get
> 
> AnonHugePages:   1048576 kB
> 
> converted to
> 
> Anonymous:       1048580 kB
> 
> Which makes sense (no memory optimized out) as discussed above.

Yes, my reproducer also shows exactly that. It's clear a lot of work is
done but no memory is actually optimized out ;)

> 
> 
> [1] https://lkml.kernel.org/r/20250905141137.3529867-1-david@redhat.com
> 
>>
>> So, let's add an early folio_test_mlocked() check to skip this case.
>>
>> Signed-off-by: Lance Yang <lance.yang@linux.dev>
>> ---
>>   mm/huge_memory.c | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>> index 77f0c3417973..d2e84015d6b4 100644
>> --- a/mm/huge_memory.c
>> +++ b/mm/huge_memory.c
>> @@ -4183,6 +4183,9 @@ static unsigned long deferred_split_scan(struct 
>> shrinker *shrink,
>>           bool underused = false;
>>           if (!folio_test_partially_mapped(folio)) {
>> +            /* An mlocked folio is not a candidate for the shrinker. */
> 
> /*
>   * See try_to_map_unused_to_zeropage(): we cannot optimize zero-filled
>   * pages after splitting an mlocked folio.
>   */

Got it. I'll update the changelog and this comment as suggested.

> 
>> +            if (folio_test_mlocked(folio))
>> +                goto next;
>>               underused = thp_underused(folio);
>>               if (!underused)
>>                   goto next;
> 
>

Cheers,
Lance


  reply	other threads:[~2025-09-08  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08  4:07 [PATCH 1/1] mm: avoid processing mlocked THPs in deferred split shrinker Lance Yang
2025-09-08  7:38 ` David Hildenbrand
2025-09-08  8:13   ` Lance Yang [this message]
2025-09-08  8:33     ` David Hildenbrand

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=bc1182e7-3f70-4645-b8c4-a97898e57041@linux.dev \
    --to=lance.yang@linux.dev \
    --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=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=npache@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=usamaarif642@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.