__swap_cache_replace_folio(9)

👑 __swap_cache_replace_folio(9) 👑

okay so this is a Kernel API Manual page, and it's giving “we are replacing a folio in the swap cache” realness. not me being obsessed with folio replacement 💅

---

🌸 NAME 🌸

__swap_cache_replace_folio — replace a folio in the swap cache. periodt. 💖

✨ SYNOPSIS ✨

void __swap_cache_replace_folio (struct swap_cluster_info *ci , struct
folio *old , struct folio *new );

🎀 ARGUMENTS 🎀

• ci — the locked swap cluster. like, it's already locked, bestie 🔒
• old — the old folio to be replaced. bye-bye old one 👋
• new — the new folio. hiii new one ✨

🦋 DESCRIPTION 🦋

so the whole vibe is: replace an existing folio in the swap cache with a new folio. 🦋

The caller is responsible for setting up the new folio's flag and swap entries — that setup is literally on you, not on this function. Replacement will take the new folio's swap entry value as the starting offset to override all slots covered by the new folio. no cap, that's the whole description. 💅

💅 CONTEXT 💅

The caller must ensure both folios are locked, and must lock the cluster that holds the old folio to be replaced. like, these locks are non-negotiable 🔒🔒

🔥 SEE ALSO 🔥

The kernel file is ./mm/swap_state.c, and the related-pages group chat is:

• swap_cache_get_folio(9)
• swap_cache_has_folio(9)
• swap_cache_get_shadow(9)
• __swap_cache_add_check(9)
• __swap_cache_add_folio(9)
• __swap_cache_del_folio(9)
• swap_cache_del_folio(9)
• swap_cache_alloc_folio(9)
• swap_update_readahead(9)
• swapin_sync(9)
• swap_cluster_readahead(9)
• swap_vma_readahead(9)
• swapin_readahead(9)

---

okay that's the page 🫶 source/version: ./mm, date: October 2026, and the page name is __swap_cache_replace_folio(9). mwah 💋