ib_umem_get_cq_buf(9)

🎀 ib_umem_get_cq_buf 🎀

okay so this is a Kernel API Manual page and the vibe is "Pin a CQ buffer umem from per-command attributes." bestie, let's go 💅✨

🌸 NAME 🌸

ib_umem_get_cq_buf — Pin a CQ buffer umem from per-command attributes.

✨ SYNOPSIS ✨

       struct ib_umem * ib_umem_get_cq_buf (struct ib_device *device , const
       struct uverbs_attr_bundle *attrs , size_t size , int access );

💖 ARGUMENTS 💖

• device — the IB device. main character device energy.
• attrs — the uverbs attribute bundle (and yes, it may be NULL, no cap).
• size — minimum required CQ buffer length. like, the floor, bestie.
• access — IB access flags.

🦋 DESCRIPTION 🦋

So it resolves the CQ buffer from the new UMEM attribute or the legacy CQ buffer attributes. That's the whole slay.

🚨 Important vibe check: there is no UHW VA fallback, so when no source is available, the caller must arrange its own backing (typically an in-kernel allocation). not me leaving you to handle that yourself, but yes 💀

⭐ RETURN ⭐

• caller-owned umem on success
• NULL when no source supplied a buffer
• ERR_PTR(...) on error

👑 SEE ALSO 👑

• Kernel file ./drivers/infiniband/core/umem.c
• ib_umem_find_best_pgsz(9)
• ib_umem_get_desc(9)
• ib_umem_get_attr(9)
• ib_umem_get_attr_or_va(9)
• ib_umem_get_cq_buf_or_va(9)
• ib_umem_release(9)

mwah 💋 this page is from ./drivers/infiniband/core, dated October 2026. go pin that buffer and stay iconic 🫶✨