Skip to contentSkip to conversation

documentation-stop-referring-to-page_remove_rmap.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message Dec 29, 2023

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: Documentation: stop referring to page_remove_rmap()
has been removed from the -mm tree. Its filename was
documentation-stop-referring-to-page_remove_rmap.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: Documentation: stop referring to page_remove_rmap()
Date: Wed, 20 Dec 2023 23:44:55 +0100

Refer to folio_remove_rmap_*() instaed.

---

 Documentation/mm/transhuge.rst       |    2 +-
 Documentation/mm/unevictable-lru.rst |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
Documentation/mm/transhuge.rst renamed from Documentation/mm/transhuge.rst~documentation-stop-referring-to-page_remove_rmap +1 -1
@@ -156,7 +156,7 @@ Partial unmap and deferred_split_folio()
 
 Unmapping part of THP (with munmap() or other way) is not going to free
 memory immediately. Instead, we detect that a subpage of THP is not in use
-in page_remove_rmap() and queue the THP for splitting if memory pressure
+in folio_remove_rmap_*() and queue the THP for splitting if memory pressure
 comes. Splitting will free up unused subpages.
 
 Splitting the page right away is not an option due to locking context in
Documentation/mm/unevictable-lru.rst renamed from Documentation/mm/unevictable-lru.rst~documentation-stop-referring-to-page_remove_rmap +2 -2
@@ -486,7 +486,7 @@ munlock the pages if we're removing the
 Before the unevictable/mlock changes, mlocking did not mark the pages in any
 way, so unmapping them required no processing.
 
-For each PTE (or PMD) being unmapped from a VMA, page_remove_rmap() calls
+For each PTE (or PMD) being unmapped from a VMA, folio_remove_rmap_*() calls
 munlock_vma_folio(), which calls munlock_folio() when the VMA is VM_LOCKED
 (unless it was a PTE mapping of a part of a transparent huge page).
 
@@ -511,7 +511,7 @@ userspace; truncation even unmaps and de
 which had been Copied-On-Write from the file pages now being truncated.
 
 Mlocked pages can be munlocked and deleted in this way: like with munmap(),
-for each PTE (or PMD) being unmapped from a VMA, page_remove_rmap() calls
+for each PTE (or PMD) being unmapped from a VMA, folio_remove_rmap_*() calls
 munlock_vma_folio(), which calls munlock_folio() when the VMA is VM_LOCKED
 (unless it was a PTE mapping of a part of a transparent huge page).
 

_

Patches currently in -mm which might be from [email protected] are