__ib_alloc_cq(9)

💅 NAME

__ib_alloc_cq — bestie, this one allocates a completion queue ✨

This page lives in the Kernel API Manual, and it's literally all about making a CQ happen for in-kernel users 🫶

---

✨ SYNOPSIS

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

---

🎀 ARGUMENTS

okay so here's the whole cast of characters, no skips, no cuts 💖

• dev — the device you're allocating the CQ for, like obviously 🦋
• private — driver private data, and it's accessible from cq->cq_context (iykyk)
• nr_cqe — the number of CQEs to allocate 🔥
• comp_vector — HCA completion vectors for this CQ, slay
• poll_ctx — the context to poll the CQ from 💅
• caller — module owner name, periodt

---

🦋 DESCRIPTION

So this is the proper interface to allocate a CQ for in-kernel users — like, the correct one, the main character one 👑

A CQ allocated with this interface will automatically be polled from the specified context, no cap ✨

And huge heads up: the ULP must use wr->wr_cqe instead of wr->wr_id to use this CQ abstraction. Literally do not mix those up, bestie 😭

---

🌸 SEE ALSO

• ./drivers/infiniband/core/cq.c
• ib_process_cq_direct(9)
• __ib_alloc_cq_any(9)
• ib_free_cq(9)
• ib_cq_pool_get(9)
• ib_cq_pool_put(9)

---

🧚 go read the kernel file if you want the lore, it's giving source material

kisses from the ./drivers/infiniband/core girlies — October 2026 💜🎀💖