rdma_connect(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« 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:


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