folio_add_lru(9)

💅 folio_add_lru — from the Kernel API Manual, bestie

okay so real talk, this one's a kernel-function page (folio_add_lru(9)) and it's short but it's mighty, so let's get into it 🫶

---

✨ NAME ✨

folio_add_lru — literally just: add a folio to an LRU list. that's the whole vibe. 🎀

---

🌸 SYNOPSIS 🌸

void folio_add_lru (struct folio *folio );

no return value, it's a void girlie — she does the thing and dips 💅

---

🦋 ARGUMENTS 🦋

• folio — the folio that's getting added to the LRU. that's it, that's the whole argument, she's low maintenance ✨

---

🔥 DESCRIPTION 🔥

so what's actually happening: you queue the folio for addition to the LRU. not "add it right now" — queue. subtle but iconic 😌

the whole decision on whether the page goes on the [in]active [file|anon] list? highkey deferred until the folio_batch is drained. she's not rushing, she's strategising ⭐

and the reason for that little delay is genuinely cute: it gives the caller of folio_add_lru a chance to have the folio added to the active list instead, by using folio_mark_accessed. it's giving main character energy for the caller, fr fr 🧚

---

🌈 SEE ALSO 🌈

• Kernel file ./mm/folio.c
• folio_mark_accessed(9)
• folio_add_lru_vma(9)
• deactivate_file_folio(9)
• folio_mark_lazyfree(9)
• lru_cache_drain_for_folio(9)
• folios_put_refs(9)
• release_pages(9)
• folio_batch_remove_exceptionals(9)

---

okay that's the whole page, no cap 💖 she lives in ./mm, and the fine humans of the kernel docs stamped her October 2026 — so go forth and queue those folios responsibly, bestie 👑 🌸