mapping_evict_folio(9)

mapping_evict_folio(9)

okay so bestie, welcome to the Kernel API Manual entry for mapping_evict_folio(9) — this one is lowkey iconic because it’s all about safely yeeting an unused folio out of the page-cache 💅✨

---

💖 NAME 💖

mapping_evict_folio — Remove an unused folio from the page-cache. no cap, that’s the whole vibe 🎀

---

✨ SYNOPSIS ✨

long mapping_evict_folio (struct address_space *mapping , struct folio
       *folio );

---

🫶 ARGUMENTS 🫶

• mapping — The mapping this folio belongs to. like, its page-cache home address 🏠
• folio — The folio to remove. yes bestie, this is the one getting evicted 🙈

---

🌸 DESCRIPTION 🌸

Safely remove one folio from the page cache. It only drops clean, unused folios — so it’s giving careful queen, not chaotic delete energy 🧚💖

---

🔒 CONTEXT 🔒

Folio must be locked. bestie, this is not optional — lock it first or do not come crying to me 😭🔐

---

🎀 RETURN 🎀

The number of pages successfully removed. that’s the receipt, periodt 💅🧾

---

🦋 SEE ALSO 🦋

• Kernel file ./mm/truncate.c
• folio_invalidate(9)
• truncate_inode_pages_range(9)
• truncate_inode_pages(9)
• truncate_inode_pages_final(9)
• mapping_try_invalidate(9)
• invalidate_mapping_pages(9)
• invalidate_inode_pages2_range(9)
• invalidate_inode_pages2(9)
• truncate_pagecache(9)
• truncate_setsize(9)
• pagecache_isize_extended(9)
• truncate_pagecache_range(9)

---

later, bestie 💖 source/version: ./mm; date: October 2026; page: mapping_evict_folio(9) — mwah 💋✨