folio_order(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… folio_order(9) β€” from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, holding a folio, and you NEED to know how big its allocation order is. that's the whole gig. this page is your girl. ✨


🌸 NAME 🌸

folio_order β€” literally just the allocation order of a folio. that's it, that's the function. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

unsigned int folio_order (const struct folio *folio );

πŸ’œ ARGUMENTS πŸ’œ

  • folio β€” the folio. the one and only. the main character. πŸ‘‘

✨ DESCRIPTION ✨

so a folio is composed of 2^order pages β€” like, that's its whole thing. if you wanna know what "order" actually means, go read get_order. no cap, that's where the definition lives. πŸ“–


πŸ”₯ RETURN πŸ”₯

the order of the folio. slay, that's the answer. πŸ’…


🌈 SEE ALSO 🌈

okay this list is LONG, hydrate before reading, but every single one is here because they're all friends of the show 🫢 β€” kernel file ./include/linux/mm.h:

iykyk, that's a whole friend group. πŸ’€


and that's the page!! source is ./include/linux, version date October 2026 β€” mwah, iconic, no notes. πŸ“πŸ’–

πŸ“¦ where this page comes from