page_pool_is_unreadable(9)

💅 page_pool_is_unreadable — Kernel API Manual

okay so picture this: you're deep in the kernel, section 9 of the manual, and you just need to know one thing — will the buffers this page pool hands you be unreadable to the CPU? bestie, this page is literally your answer ✨

---

🎀 NAME 🎀

page_pool_is_unreadable — tells you whether the buffers it's gonna allocate will be unreadable for the CPU 👀

---

🦋 SYNOPSIS 🦋

bool page_pool_is_unreadable (struct page_pool *pool );

---

🌸 ARGUMENTS 🌸

• pool — the page pool being queried, aka the thing we're side-eyeing 💅

---

✨ DESCRIPTION ✨

so this helper checks if the page pool is gonna return buffers that are unreadable to the CPU / kernel. and lowkey that's only ever the case when user space bound a memory provider (mp) that returns unreadable memory to the queue served by the page pool. like, that's the whole scenario, fr fr 🫶

and here's the plot twist: if PP_FLAG_ALLOW_UNREADABLE_NETMEM was set but there's no mp bound, this helper will return false. not me checking twice 😭 so don't let the flag alone fool you, bestie.

also see netif_rxq_has_unreadable_mp — it's giving related-content energy 👑

---

👑 RETURN 👑

returns true if memory allocated by the page pool may be unreadable — that's it, that's the whole vibe 🎀

---

🌈 SEE ALSO 🌈

✨ Kernel file ./include/net/page_pool/helpers.h

✨ page_pool allocator(9)

✨ page_pool_dev_alloc_pages(9)

✨ page_pool_dev_alloc_frag(9)

✨ page_pool_dev_alloc(9)

✨ page_pool_dev_alloc_va(9)

✨ page_pool_get_dma_dir(9)

✨ page_pool_fragment_page(9)

✨ page_pool_put_page(9)

✨ page_pool_put_full_page(9)

✨ page_pool_recycle_direct(9)

✨ page_pool_free_va(9)

✨ page_pool_get_dma_addr(9)

✨ page_pool_dma_sync_for_cpu(9)

like, the whole page pool friend group showed up to the function reference. iconic behavior, no notes 💜

---

and that's the page, bestie 🍓 this lil gem lives in ./include/net/page_pool and it's dated October 2026 — so go forth, check your pools, and slay 💅🔥