fgf_set_order(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fgf_set_order(9) β€” like, the kernel API manual, but make it make sense ✨

okay bestie so you're in the kernel API manual, section 9, and the page you're on is literally fgf_set_order πŸŽ€ β€” and yeah, that's the same fgf_set_order(9) you saw up in the corner. come sit with me, this one's short and sweet 🫢


✨ NAME ✨

fgf_set_order β€” encodes a length in the fgf_t flags. that's it. that's the whole vibe check πŸ’…


🌸 SYNOPSIS 🌸

fgf_t fgf_set_order (size_t size );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • size β€” the suggested size of the folio you wanna create πŸ‘‘ key word: suggested. it's giving "here's my wishlist," not "here's my demand."

πŸ’– DESCRIPTION πŸ’–

so if you're the caller of __filemap_get_folio, you can use this little icon to hint at a preferred size for the folio that gets created 🌈

but bestie, listen, because this is the part where the plot twists:

  • if there's already a folio hanging out at that index, it gets returned to you, no matter what its size is 😭 like, whatever size it is, that's what you get. no notes, no negotiation.
  • if a folio gets freshly created, it may end up a totally different size than what you asked for πŸ’€ and that's not a bug, that's just… alignment constraints, memory pressure, or other folios chilling at nearby indices. the universe said "close enough" 🧚

so like, your suggestion is a suggestion. lowkey the kernel is the main character here fr fr πŸ™ˆ


πŸ’œ SEE ALSO πŸ’œ

your reading list, bestie β€” all from the Kernel file ./include/linux/pagemap.h:


ngl, that's a lot of cross-references for a function whose whole job is "put a number in some flags." but that's the filemap life, bestie πŸ“

and that's the page!! πŸ’– this lil gem lives at ./include/linux and it's dated October 2026, filed under fgf_set_order(9) β€” slay, go read your folios, ily, bye πŸŽ€πŸ”₯

πŸ“¦ where this page comes from