From: Dev Jain <dev.jain@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
akpm@linux-foundation.org, ljs@kernel.org, muchun.song@linux.dev,
osalvador@suse.de
Cc: riel@surriel.com, liam@infradead.org, vbabka@kernel.org,
harry@kernel.org, jannh@google.com, lance.yang@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ryan.roberts@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH 3/5] mm/rmap: refactor some code around lazyfree folio unmapping
Date: Thu, 9 Jul 2026 17:46:59 +0530 [thread overview]
Message-ID: <61fb2165-bc58-4c54-84b2-4ada10b19bcf@arm.com> (raw)
In-Reply-To: <22fb2f54-da23-40b2-91f5-aeaf54037bcd@kernel.org>
On 07/07/26 7:48 pm, David Hildenbrand (Arm) wrote:
> On 7/7/26 14:11, Dev Jain wrote:
>> For lazyfree folio unmapping, after clearing the ptes we must abort the
>> operation if the folio got dirtied or it has unexpected references.
>>
>> Refactor this logic into a function which will return whether we need
>> to abort or not.
>>
>> If we abort, we restore the ptes and bail out of try_to_unmap_one.
>> Otherwise adjust the rss stats of the mm and jump to a label.
>>
>> Also rename that label from "discard" to "finish_unmap"; the former
>> is appropriate in the lazyfree context, but the code following the label
>> is executed for other successful unmap code paths too, so 'discard' does
>> not sound correct for them.
>>
>> No functional change intended.
>>
>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>> ---
>> mm/rmap.c | 87 +++++++++++++++++++++++++++++++------------------------
>> 1 file changed, 49 insertions(+), 38 deletions(-)
>>
>> diff --git a/mm/rmap.c b/mm/rmap.c
>> index 934773dfa2f2a..00b571c2a1bab 100644
>> --- a/mm/rmap.c
>> +++ b/mm/rmap.c
>> @@ -2067,6 +2067,52 @@ static bool try_to_unmap_hugetlb_one(struct folio *folio,
>> return ret;
>> }
>>
>> +static inline bool ttu_anon_lazyfree_folio(struct vm_area_struct *vma,
>> + struct folio *folio)
>> +{
>> + int ref_count, map_count;
>> +
>> + /*
>> + * Synchronize with gup_pte_range():
>> + * - clear PTE; barrier; read refcount
>> + * - inc refcount; barrier; read PTE
>> + */
>> + smp_mb();
>> +
>> + ref_count = folio_ref_count(folio);
>> + map_count = folio_mapcount(folio);
>> +
>> + /*
>> + * Order reads for page refcount and dirty flag
>> + * (see comments in __remove_mapping()).
>> + */
>> + smp_rmb();
>> +
>> + if (folio_test_dirty(folio) && !(vma->vm_flags & VM_DROPPABLE)) {
>> + /*
>> + * redirtied either using the page table or a previously
>> + * obtained GUP reference.
>> + */
>> + folio_set_swapbacked(folio);
>> + return false;
>> + }
>> +
>> + if (ref_count != 1 + map_count) {
>> + /*
>> + * Additional reference. Could be a GUP reference or any
>> + * speculative reference. GUP users must mark the folio
>> + * dirty if there was a modification. This folio cannot be
>> + * reclaimed right now either way, so act just like nothing
>> + * happened.
>> + * We'll come back here later and detect if the folio was
>> + * dirtied when the additional reference is gone.
>> + */
>> + return false;
>> + }
>> +
>> + return true;
>
> You could simply do
>
>
> /*
> * Additional references could be due to GUP or from a speculative
> * lookup. ...
Are you also suggesting to shorten the comment?
> */
> return ref_count == 1 + map_count;
Yes much better.
>
>
> Nothing else jumped at me
>
> Acked-by: David Hildenbrand (Arm) <david@kernel.org>
>
next prev parent reply other threads:[~2026-07-09 12:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 12:11 [PATCH 0/5] mm/rmap: Refactor try_to_unmap_one Dev Jain
2026-07-07 12:11 ` [PATCH 1/5] mm/rmap: convert page -> folio for hwpoison checks Dev Jain
2026-07-07 14:06 ` David Hildenbrand (Arm)
2026-07-07 12:11 ` [PATCH 2/5] mm/rmap: Add try_to_unmap_hugetlb_one Dev Jain
2026-07-07 14:15 ` David Hildenbrand (Arm)
2026-07-09 12:15 ` Dev Jain
2026-07-07 12:11 ` [PATCH 3/5] mm/rmap: refactor some code around lazyfree folio unmapping Dev Jain
2026-07-07 14:18 ` David Hildenbrand (Arm)
2026-07-09 12:16 ` Dev Jain [this message]
2026-07-09 13:43 ` David Hildenbrand (Arm)
2026-07-07 12:11 ` [PATCH 4/5] mm/rmap: refactor anon swapbacked folio unmap in try_to_unmap_one Dev Jain
2026-07-07 14:26 ` David Hildenbrand (Arm)
2026-07-09 13:39 ` Dev Jain
2026-07-07 12:11 ` [PATCH 5/5] mm/rmap: add anon folio unmap dispatcher function Dev Jain
2026-07-07 14:28 ` David Hildenbrand (Arm)
2026-07-09 13:34 ` Dev Jain
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=61fb2165-bc58-4c54-84b2-4ada10b19bcf@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@kernel.org \
--cc=harry@kernel.org \
--cc=jannh@google.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=vbabka@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