migrate_folio(9)

📦 version 7.3.1, in nixpkgs unstable

✨ migrate_folio(9) ✨

okay so this is a page from the Kernel API Manual, and tbh it's a whole mood: it's the little helper that does migrate_folio — simple folio migration. 💅

🌸 NAME 🌸

migrate_folio — Simple folio migration. that's it, that's the vibe. short, sweet, slays. 🎀

🦋 SYNOPSIS 🦋

int migrate_folio (struct address_space *mapping , struct folio *dst ,
struct folio *src , enum migrate_mode mode );

like, it returns an int bestie, don't forget that part 👑

💖 ARGUMENTS 💖

  • mapping — the address_space that's holding the folio. it's giving "where does this live" energy.
  • dst — the folio you're migrating the data to. the destination, the new home, the main character 🏠✨
  • src — the folio that's holding the current data right now. the one being moved out, rip 🥲
  • mode — an enum migrate_mode, aka how to migrate the folio. the vibe check for the whole operation.

🔥 DESCRIPTION 🔥

So this is the common logic to directly migrate a single LRU folio, and it's specifically suitable for folios that do not have private data. no private data? then this is literally your girl 🫶

Also super important, no cap: folios are locked upon entry and exit. 🔒 so you walk in locked and you walk out locked, periodt.

🌈 SEE ALSO 🌈

Kernel file ./mm/migrate.c, plus these iconic little friends:

iykyk, go read them next 💜

🦋 ok that's the whole page bestie, ily, go migrate some folios responsibly 🎀

source lives in ./mm, dated October 2026, and yes this was migrate_folio(9) the whole time 😭💖

📦 where this page comes from