rdma_accept(9)

🌸 NAME 🌸

okay bestie, welcome to the Kernel API Manual entry for rdma_accept — the routine you call to accept a connection request or response. yes, both. it's giving flexible icon behavior 💅

---

✨ SYNOPSIS ✨

int rdma_accept (struct rdma_cm_id *id , struct rdma_conn_param
*conn_param );

---

🎀 ARGUMENTS 🎀

• id — the connection identifier associated with the request. it's literally the main character of this call 🫶
• conn_param — all the info needed to establish the connection. this must be provided if you're accepting a connection request. but if you're accepting a connection response, this parameter must be NULL. no cap, those are different vibes 🙈

---

🦋 DESCRIPTION 🦋

typically, this routine is only called by the listener to accept a connection request. but bestie, it also must be called on the active side of a connection if the user is performing their own QP transitions. so don't ghost it on that side either ✨

in the case of error, a reject message is sent to the remote side and the state of the qp associated with the id is modified to error, such that any previously posted receive buffers would be flushed. so yeah, error path is real and it flushes your buffers — noted 💀

this function is for use by kernel ULPs and must be called from under the handler callback. like, that's not optional, bestie. it's giving "read the assignment before you submit" energy 😭

---

🔥 SEE ALSO 🔥

kernel file ./drivers/infiniband/core/cma.c — and then all the related besties you might wanna check out:

• rdma_is_consumer_reject(9)
• rdma_iw_cm_id(9)
• cma_acquire_dev_by_src_ip(9)
• cma_ib_acquire_dev(9)
• rdma_set_ack_timeout(9)
• rdma_set_min_rnr_timer(9)
• rdma_connect_locked(9)
• rdma_connect(9)
• rdma_connect_ece(9)

---

mwah 💋 — brought to you by ./drivers/infiniband/core, dated October 2026, and forever known as rdma_accept(9). slay and read the callback rules 🎀💖