From: David Hildenbrand <david@redhat.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>, akpm@linux-foundation.org
Cc: willy@infradead.org, hannes@cmpxchg.org, 21cnbao@gmail.com,
ryan.roberts@arm.com, ziy@nvidia.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: huge_memory: add folio_mark_accessed() when zapping file THP
Date: Wed, 9 Apr 2025 11:53:13 +0200 [thread overview]
Message-ID: <cb8fee50-4dd2-4362-b716-bf1e921bdfa2@redhat.com> (raw)
In-Reply-To: <0e294c56-d924-4d40-aa24-584235e8c923@linux.alibaba.com>
On 09.04.25 11:49, Baolin Wang wrote:
>
>
> On 2025/4/9 17:46, David Hildenbrand wrote:
>> On 09.04.25 11:38, Baolin Wang wrote:
>>> When investigating performance issues during file folio unmap, I
>>> noticed some
>>> behavioral differences in handling non-PMD-sized folios and PMD-sized
>>> folios.
>>> For non-PMD-sized file folios, it will call folio_mark_accessed() to
>>> mark the
>>> folio as having seen activity, but this is not done for PMD-sized folios.
>>>
>>> This might not cause obvious issues, but a potential problem could be
>>> that,
>>> it might lead to reclaim hot file folios under memory pressure, as quoted
>>> from Johannes:
>>>
>>> "
>>> Sometimes file contents are only accessed through relatively short-lived
>>> mappings. But they can nevertheless be accessed a lot and be hot. It's
>>> important to not lose that information on unmap, and end up kicking out a
>>> frequently used cache page.
>>> "
>>>
>>> Therefore, we should also add folio_mark_accessed() for PMD-sized file
>>> folios when unmapping.
>>>
>>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>>> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
>>> Acked-by: Zi Yan <ziy@nvidia.com>
>>> ---
>>> Changes from RFC:
>>> - Update the commit message, per Johannes.
>>> - Collect Acked tags from Johannes and Zi. Thanks.
>>> ---
>>> mm/huge_memory.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>> index 2a47682d1ab7..955781b4e946 100644
>>> --- a/mm/huge_memory.c
>>> +++ b/mm/huge_memory.c
>>> @@ -2260,6 +2260,10 @@ int zap_huge_pmd(struct mmu_gather *tlb, struct
>>> vm_area_struct *vma,
>>> zap_deposited_table(tlb->mm, pmd);
>>> add_mm_counter(tlb->mm, mm_counter_file(folio),
>>> -HPAGE_PMD_NR);
>>> +
>>> + if (flush_needed && pmd_young(orig_pmd) &&
>>> + likely(vma_has_recency(vma)))
>>> + folio_mark_accessed(folio);
>>
>> So the flush_needed check is really just a pmd_present() check. (the
>> latter would be clearer, but I don't mind)
>
> Yes, we've already checked pmd_present() before, so I assume the
> flush_needed check is cheaper:)
Maybe :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-09 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 9:38 Baolin Wang
2025-04-09 9:46 ` David Hildenbrand
2025-04-09 9:49 ` Baolin Wang
2025-04-09 9:53 ` David Hildenbrand [this message]
2025-04-10 8:45 ` Oscar Salvador
2025-04-11 1:07 ` Baolin Wang
2025-04-11 3:14 ` Oscar Salvador
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=cb8fee50-4dd2-4362-b716-bf1e921bdfa2@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.org \
--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