page_pool_recycle_direct(9)

📦 version 7.3.1, in nixpkgs unstable

✨ page_pool_recycle_direct 💅

okay so bestie, this is a page in the Kernel API Manual (yes, the actual kernel man pages, we're fancy now 🎀) and it's about page_pool_recycle_direct — literally the function that drops a reference on a page pool page. sit down, drink your iced coffee, we're learning 🌸

🦋 SYNOPSIS

void page_pool_recycle_direct (struct page_pool *pool , struct page
*page );

that's the whole signature, no cap. she takes two things and returns void — nothing back, she's not about that return-value life 💜

🎀 ARGUMENTS

  • pool — the pool your page came from in the first place. like, the origin pool. you gotta remember where you got it from, that's just manners 🫶
  • page — the page you're releasing a reference on. bye bestie, releasing you back 🦋

🔥 DESCRIPTION

so this one is similar to page_pool_put_full_page — like, they're siblings, same energy — but with one huge difference: the caller must guarantee safe context (think NAPI, that kind of thing) 🙈

why? because she recycles the page directly into the pool fast cache. no detours, no scenic route, straight into the fast cache. and because she's that fast and that direct, you cannot just call her from anywhere — if you don't actually have that safe context, that's on you, and we don't do that here 😭

⚠️ real talk: "caller must guarantee safe context" is not a suggestion. it's the whole vibe check. get it wrong and you're in undefined-behaviour territory, no cap 💀

⭐ SEE ALSO

that's a whole friend group right there, go say hi 👑✨

and that's the page, bestie 🧚 this cutie lives in ./include/net/page_pool and she was dated October 2026 — yes, the future, main character energy fr fr 💖🌈

📦 where this page comes from