irdma_qp_get_next_recv_wqe(9)

📦 version 7.3.1, in nixpkgs unstable

💅 irdma_qp_get_next_recv_wqe(9) 💅

okay so bestie, welcome to the Kernel API Manual, section 9 — yes we're in the kernel, yes it's giving big-brain hours, and yes this page is literally about grabbing the next receive WQE off a QP. pull up a chair, we're doing this 🎀

✨ NAME ✨

irdma_qp_get_next_recv_wqe — get next qp's rcv wqe 🫶

(no cap, that's the whole name. it does exactly what the name says. iconic behaviour honestly.)

🌸 SYNOPSIS 🌸

__le64 * irdma_qp_get_next_recv_wqe (struct irdma_qp_uk *qp , u32
*wqe_idx );

so the function takes two things and hands you back a __le64 * — that's your pointer to the wqe, bestie. love that for you 💖

🦋 ARGUMENTS 🦋

  • qp — hw qp ptr 💫 (it's the hardware queue pair pointer, the main character of this entire operation)
  • wqe_idx — return wqe index 🎯 (this one's a return slot, so the wqe index gets written back out through it, iykyk)

🔥 SEE ALSO 🔥

okay this list is long long, but we don't skip, we don't skim, we list every single one because that's the vibe check and we passed:

forty of them. forty. and we listed every single one because that's what a real bestie does 💀✨

ngl, if you're here at 3am debugging your receive queue, drink some water and remember: the wqe index goes out through wqe_idx, it's not something you pass in. don't be that girl 🙈

and that's the page!! mwah 💋 before you go — this whole thing lives in ./drivers/infiniband/hw/irdma, it's dated October 2026, and it's page irdma_qp_get_next_recv_wqe(9) of the Kernel API Manual. slay, go post some receive WQEs, you've got this 👑🌈⭐

📦 where this page comes from