folio_mark_accessed(9)

💅 folio_mark_accessed(9) 💅

okay so this is from the Kernel API Manual, and bestie, it's giving “tiny function, very specific job.” Let's get into it. 🦋

✨ NAME ✨

folio_mark_accessed — mark a folio as having seen activity. that's it, that's the job. 💖

🎀 SYNOPSIS 🎀

void folio_mark_accessed (struct folio *folio );

🌸 ARGUMENTS 🌸

• folio — the folio you're marking. the one and only argument, slay. 💅

🦋 DESCRIPTION 🦋

This function will perform one of the following transitions — pick your lane, folio bestie:

• inactive,unreferenced -> inactive,referenced
• inactive,referenced -> active,unreferenced
• active,unreferenced -> active,referenced

When a newly allocated folio is not yet visible, so safe for non-atomic ops, __folio_set_referenced may be substituted for folio_mark_accessed. iykyk: freshly allocated, not-yet-visible folio, non-atomic-ops-safe situation. ✨

🔥 SEE ALSO 🔥

Kernel file ./mm/folio.c:

• folio_add_lru(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)

mwah 💋 that's the whole page, bestie. source/version is ./mm, dated October 2026, and the function is folio_mark_accessed(9). 🫶🎀