rpma_conn_get_cq(3)

💖 rpma_conn_get_cq — get the connection's main CQ 💖

okay bestie, welcome to the RPMA Programmer's Manual ✨ this one's short and sweet, like a lil snack, but it's important so pay attention 🫶

---

🌸 NAME 🌸

rpma_conn_get_cq — grab the connection's main CQ, no cap 👑

---

✨ SYNOPSIS ✨

#include <librpma.h>

struct rpma_conn;
struct rpma_cq;
int rpma_conn_get_cq(const struct rpma_conn *conn, struct rpma_cq **cq_ptr);

---

🦋 DESCRIPTION 🦋

so like. rpma_conn_get_cq() gets the main CQ from the connection. that's it. that's the whole job. 💅

but here's the tea on when it matters, bestie, because context is everything:

• when the receive CQ is not present, the main CQ lets you handle all completions within the connection ✨
• when the receive CQ is present, the main CQ lets you handle all completions except rpma_recv(3) completions within the connection 🙈

and if you wanna know the deets about the receive CQ itself, go check rpma_conn_get_rcq(3), she's the main character of that page 💖

---

⭐ RETURN VALUE ⭐

• returns 0 on success 🎉
• returns a negative error code on failure 😭
• and listen: rpma_conn_get_cq() does not set the *cq_ptr value on failure. like, it just leaves it alone. respect the boundary ✋

---

💀 ERRORS 💀

rpma_conn_get_cq() can fail with this one error, and honestly it's giving "you passed me a NULL":

• RPMA_E_INVAL — conn or cq_ptr is NULL 🫠

fr fr, double-check your pointers before you call this. NULL is not a vibe.

---

👑 SEE ALSO 👑

go read these next, bestie, they're all connected (pun fully intended):

• rpma_conn_req_connect(3)
• rpma_conn_get_rcq(3)
• rpma_cq_wait(3)
• rpma_cq_get_wc(3)
• rpma_cq_get_fd(3)
• rpma_recv(3)
• librpma(7)
• https://pmem.io/rpma/

---

and that's the whole page, no notes 💅 this was RPMA, dated 01 April 2024, and you just read rpma_conn_get_cq(3) — slay, you're literally a systems programmer now 🎀💖✨🦋🌸