rdma_connect_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 rdma_connect_locked(9) β€” a Kernel API Manual moment 🌸

okay so bestie, welcome to the Kernel API Manual entry for rdma_connect_locked(9) β€” yes the (9) is part of the name, it's giving section-nine energy and we respect it πŸ’…


✨ NAME ✨

rdma_connect_locked β€” literally just Initiate an active connection request. no cap, that's the whole vibe 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

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

look at her. she returns an int, she takes two pointers, she's iconic πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • id β€” the Connection identifier to connect. that's your main character right there, the thing you're actually connecting 🌟
  • conn_param β€” Connection information used for connected QPs. all the deets your connected QPs need to know, packed up cute πŸ“

πŸ’œ DESCRIPTION πŸ’œ

So she's Same as rdma_connect β€” same energy, same job β€” BUT (and this is the important part, don't skip it πŸ™ˆ) she can only be called from the RDMA_CM_EVENT_ROUTE_RESOLVED handler callback.

fr fr, that's a hard requirement, not a suggestion. if you're not inside that handler callback, this is not your function, bestie. rdma_connect_locked is the locked one for a reason and we do not play with that πŸ”₯

🌈 SEE ALSO 🌈

the whole friend group, assembled πŸ’– and also the Kernel file ./drivers/infiniband/core/cma.c:


and that's the page!! 🧚✨

cute little sign-off from the source at ./drivers/infiniband/core, dated October 2026, filed under rdma_connect_locked(9) β€” mwah, go slay your connection request πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from