idpf_rx_sing...hw_alloc_all(9)

📦 version 7.3.1, in nixpkgs unstable

💅 idpf_rx_singleq_buf_hw_alloc_all 💅

Okay so bestie, welcome to the Kernel API Manual — this is the page for idpf_rx_singleq_buf_hw_alloc_all(9), and honestly? It's giving "I replace used receive buffers so your network card doesn't just sit there looking tragic." Let's get into it. 🦋

✨ NAME ✨

idpf_rx_singleq_buf_hw_alloc_all — replace used receive buffers, no cap. That's literally the whole job. 🎀

🌸 SYNOPSIS 🌸

bool idpf_rx_singleq_buf_hw_alloc_all (struct idpf_rx_queue *rx_q , u16
cleaned_count );

💖 ARGUMENTS 💖

  • rx_q — the queue where we're putting the new hardware buffers back. Think of it as the main character queue that needs its glow-up. ✨
  • cleaned_count — the number of buffers we need to replace. Literally just "how many, bestie?" 🔢

🔥 DESCRIPTION 🔥

So here's the vibe check: this function returns false if all the allocations were successful, and true if any of them fail. 🫶

⚠️ Yes bestie, I know — false means success and true means something went wrong. That's the API's choice and we respect it, even if it's a little chaotic. Deal with it. 💀

👑 SEE ALSO 👑

The kernel file that this lives in is:

  • ./drivers/net/ethernet/intel/idpf/idpf_singleq_txrx.c

And fr fr, here's the whole squad of related functions — every single one, because we don't gatekeep here:

✨ That's the whole page, bestie. Now go replace those buffers and slay. ✨

This page is chillin' in ./drivers/net/ethernet/intel/idpf, and the version date is October 2026 — so yeah, it's lowkey from the future. 💜

idpf_rx_sing...hw_alloc_all(9) 🫶

📦 where this page comes from