folio_add_pin(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– folio_add_pin(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so real talk, this one's from the Kernel API Manual and it's short but it's important, so pay attention for like two seconds 🫢


✨ NAME ✨

folio_add_pin β€” literally just "try to get an additional pin on a pinned folio". that's it. that's the whole vibe πŸ’…


🌸 SYNOPSIS 🌸

void folio_add_pin (struct folio *folio );

yes girl, void return, so nothing comes back out β€” it just does the thing ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • folio β€” the folio that's getting pinned. the main character of this whole operation πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

so here's the tea: you hit up folio_add_pin when you want an additional pin on a folio that you already have a pin on. no cap β€” it's the "one more won't hurt" of the folio world πŸ“

and the little exception that eats: if the folio is a zero_page, this function makes no change at all. absolutely nothing. it's giving "saw it, didn't care" πŸ’€


🌈 SEE ALSO 🌈

bestie this list is long, so buckle up. it's all the siblings and adjacent besties over in the Kernel file ./mm/gup.c:

like, go read all of them, i'll wait πŸ’… ngl that's the whole friend group right there πŸ”₯


πŸ’‘ tiny vibe check: this page lives under ./mm, dated October 2026 β€” so when you're citing it in your notes, that's the source and the date, periodt πŸ‘‘

hope that slayed for you, mwah πŸ˜­πŸ’– πŸŒΈπŸ¦‹βœ¨

πŸ“¦ where this page comes from