__ib_alloc_cq_any(9)

✨ NAME ✨

okay so welcome to the Kernel API Manual page for __ib_alloc_cq_any(9), bestie — this one is all about how to allocate a completion queue 💅

🌸 SYNOPSIS 🌸

struct ib_cq * __ib_alloc_cq_any (struct ib_device *dev , void *private
       , int nr_cqe , enum ib_poll_context poll_ctx , const char *caller );

🎀 ARGUMENTS 🎀

• dev — the device to allocate the CQ for 🫶
• private — driver private data, accessible from cq->cq_context ✨
• nr_cqe — number of CQEs to allocate 🔢
• poll_ctx — context to poll the CQ from 👀
• caller — module owner name 🏷️

🦋 DESCRIPTION 🦋

so the whole vibe here is: attempt to spread ULP Completion Queues over each device's interrupt vectors 🌈 and honestly? it's giving "let's distribute the CQ love across those vectors" 💖

the mechanism is a simple best-effort one — no cap, that's literally what the page says, and that's the whole description, bestie 🧚

💖 SEE ALSO 💖

• Kernel file ./drivers/infiniband/core/cq.c
• ib_process_cq_direct(9)
• __ib_alloc_cq(9)
• ib_free_cq(9)
• ib_cq_pool_get(9)
• ib_cq_pool_put(9)

okay that's the whole page, bestie 🫶 source/version ./drivers/infiniband/core, dated October 2026, page __ib_alloc_cq_any(9) — mwah 💋✨