rpma_conn_req_new(3)

💖 rpma_conn_req_new 💖

okay bestie, welcome to the RPMA Programmer's Manual ✨ this one's about rpma_conn_req_new(3) and honestly? it's giving main character energy because it's literally the thing that starts the whole connection era. let's get into it 🫶

---

✨ NAME ✨

rpma_conn_req_new — create a new outgoing connection request object 💌

---

🌸 SYNOPSIS 🌸

#include <librpma.h>

struct rpma_peer;
struct rpma_conn_cfg;
struct rpma_conn_req;
int rpma_conn_req_new(struct rpma_peer *peer, const char *addr, const char *port,
                const struct rpma_conn_cfg *cfg, struct rpma_conn_req **req_ptr);

---

🦋 DESCRIPTION 🦋

so rpma_conn_req_new() does the thing: it creates a brand new outgoing connection request object 💅 and it does that using reliable, connection-oriented and message-based (RDMA_PS_TCP) QP communication. no cap, that's the whole vibe.

---

⭐ RETURN VALUE ⭐

rpma_conn_req_new() returns 0 on success or a negative error code on failure 😭 and listen — on failure it does not set the *req_ptr value. like, it just leaves it alone. rude but honest.

if cfg is NULL, then the default values are used 🌈

• see rpma_conn_cfg_new(3) for more details 👑

---

💀 ERRORS 💀

rpma_conn_req_new() can fail with the following errors:

• RPMA_E_INVAL — peer, addr, port or req_ptr is NULL 🙈
• RPMA_E_NOMEM — out of memory 😵
• RPMA_E_PROVIDER — rdma_create_id(3), rdma_resolve_addr(3), rdma_resolve_route(3) or ibv_create_cq(3) failed 💔

---

🎀 SEE ALSO 🎀

rpma_conn_cfg_new(3), rpma_conn_req_connect(3), rpma_conn_req_delete(3), rpma_conn_req_recv(3), rpma_ep_next_conn_req(3), rpma_peer_new(3), librpma(7) and https://pmem.io/rpma/ 🧚

---

and that's the whole page bestie, we ate and left no crumbs 🍓 this was RPMA, dated 01 April 2024, and it's rpma_conn_req_new(3) — go create some connection requests, you've got this 💜✨