folio_can_map_prot_numa(9)

📦 version 7.3.1, in nixpkgs unstable

💅 folio_can_map_prot_numa — like, the vibe check for prot NUMA mapping

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little function from ./mm and honestly? she's a gatekeeper. let's get into it.

🌸 NAME 🌸

folio_can_map_prot_numa — the function that checks whether the folio can map prot numa. literally its whole job. no cap.

✨ SYNOPSIS ✨

bool folio_can_map_prot_numa (struct folio *folio , struct
       vm_area_struct *vma , bool is_private_single_threaded );

she returns a bool, she takes three args, and she's judging your folio. periodt.

🎀 ARGUMENTS 🎀

  • folio — the folio whose mapping is being considered for being made NUMA hintable. yes, that's the actual wording, this is her moment, we're considering her for hintability 💖
  • vma — the VMA that the folio belongs to. her home, her context, her main character energy.
  • is_private_single_threaded — is this a single-threaded private VMA or not? just a yes/no, but make it fashion 🦋

🔥 DESCRIPTION 🔥

so what does she actually do? she checks to see if the folio actually indicates that we need to make the mapping one which causes a NUMA hinting fault 👑

because ngl, there are cases where it's simply unnecessary — and in those cases, no fault, no drama. and when prot numa is needed, the folio's access time is adjusted for memory tiering. the way that she just... tidies up behind the scenes. iconic. 🌈

⭐ RETURN ⭐

  • True if the mapping of the folio needs to be changed 💅
  • false otherwise 🙈

that's it. that's the whole return. clean, simple, ate.

🫶 SEE ALSO 🫶

kernel file ./mm/mempolicy.c and her whole friend group:

go read them all fr fr, they're giving encyclopedia but make it slay 💜

and that's the page bestie!! brought to you by ./mm on October 2026 — mwah, go forth and map responsibly 🧚💖

📦 where this page comes from