mm-memory-use-folio_mapcount-in-zap_present_folio_ptes.patch removed from -mm tree
The quilt patch titled
Subject: mm/memory: use folio_mapcount() in zap_present_folio_ptes()
has been removed from the -mm tree. Its filename was
mm-memory-use-folio_mapcount-in-zap_present_folio_ptes.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: David Hildenbrand <[email protected]>
Subject: mm/memory: use folio_mapcount() in zap_present_folio_ptes()
Date: Tue, 9 Apr 2024 21:22:50 +0200
We want to limit the use of page_mapcount() to the places where it is absolutely necessary. In zap_present_folio_ptes(), let's simply check the folio mapcount(). If there is some issue, it will underflow at some point either way when unmapping.
As indicated already in commit 10ebac4f95e7 ("mm/memory: optimize unmap/zap with PTE-mapped THP"), we already documented "If we ever have a cheap folio_mapcount(), we might just want to check for underflows there.".
There is no change for small folios. For large folios, we'll now catch more underflows when batch-unmapping, because instead of only testing the mapcount of the first subpage, we'll test if the folio mapcount underflows.
---
mm/memory.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
mm/memory.c renamed from mm/memory.c~mm-memory-use-folio_mapcount-in-zap_present_folio_ptes +1 -2
@@ -1502,8 +1502,7 @@ static __always_inline void zap_present_if (!delay_rmap) {folio_remove_rmap_ptes (folio, page, nr, vma); -/* Only sanity-check the first page in a batch. */ -if (unlikely (page_mapcount (page) <0 )) +if (unlikely (folio_mapcount (folio) <0 ))print_bad_pte (vma, addr, ptent, page); }
_
Patches currently in -mm which might be from [email protected] are