rdma_connect(9)
π« rdma_connect(9) β Kernel API Manual, bestie edition π«
okay so this is rdma_connect, from the Kernel API Manual, and honestly? she's kind of a big deal. active connection requests, remote QPs, the whole vibe. let's get into it π«Ά
β¨ NAME β¨
rdma_connect β literally Initiate an active connection request. that's the whole job and she does it slayfully π
πΈ SYNOPSIS πΈ
int rdma_connect (struct rdma_cm_id *id , struct rdma_conn_param
*conn_param );
π ARGUMENTS π
idβ the Connection identifier that you're connecting. it's the main character of this whole operation ngl πconn_paramβ Connection information used for connected QPs. the little bundle of details that rides along β¨
π¦ DESCRIPTION π¦
okay so before you even think about calling this, you have to have resolved a route for the rdma_cm_id you're connecting with β like, you literally must have called rdma_resolve_route first. no route, no connect, that's the rule π¨
then this call does one of two things, depending on the vibe:
- it either connects to a remote QP, or
- it obtains remote QP information for unconnected
rdma_cm_id's
and which one actually happens? it's based on the rdma_cm_id's port space. that's the deciding factor, periodt π―
fr fr, don't skip the rdma_resolve_route step β this routine expects it to have already happened π
π SEE ALSO π
Kernel file ./drivers/infiniband/core/cma.c β and the whole friend group:
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_ece(9)rdma_accept(9)
and that's the page!! π§ this iconic little number lives in ./drivers/infiniband/core, and the version you're reading is the October 2026 one β mwah, tysm for reading, ily, go resolve that route bestie πππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms