page_pool_put_netmem_bulk(9)

💅 page_pool_put_netmem_bulk — from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, it's giving page_pool energy, and you've got a whole pile of netmem references that you need to let go of. that's this function. she's the "release references on multiple netmems" girlie, and yes she slays. ✨

---

🌸 SYNOPSIS 🌸

void page_pool_put_netmem_bulk (netmem_ref *data , u32 count );

that's it. two arguments, zero drama. 🎀

---

💖 ARGUMENTS 💖

• data — the array that's holding your netmem references. it's literally the whole lineup of netmems you're about to release, bestie. 🦋
• count — how many entries are actually in data. like, how many of the girls are showing up to the party. 🔥

---

✨ DESCRIPTION ✨

so what does she actually do? 💅

she tries to refill a number of netmems back into the ptr_ring cache, and she does it while holding the ptr_ring producer lock. get you a function that can multitask. 👑

but here's the plot twist: if the ptr_ring is full, page_pool_put_netmem_bulk will release the leftover netmems to the memory provider instead. so nobody gets left behind — they just get handed off somewhere else. iconic behavior honestly. 🌈

she's built for a very specific vibe: page_pool_put_netmem_bulk is suitable to be run inside the driver NAPI tx completion loop for the XDP_REDIRECT use case. that's the main character energy right there. ⭐

🚨 bestie pls read this — the caller must not use the data area after running page_pool_put_netmem_bulk, because this function overwrites it. like, it's gone. don't come back looking for it. 😭

---

👀 SEE ALSO 👀

• Kernel file ./net/core/page_pool.c
• page_pool_get_stats(9)
• page_pool_create_percpu(9)
• page_pool_create(9)
• page_pool_enable_direct_recycling(9)

the whole friend group, fr fr. 🫶

---

and that's the page, babe 💜 — brought to you straight out of ./net/core, dated October 2026, from the Kernel API Manual itself. go forth and release those netmems responsibly. 🧚‍♀️🌷