STRUCT RTRS_MSG_CONN_REQ(9)
β¨ NAME β¨
struct rtrs_msg_conn_req β Client connection request to the server π
okay so bestie, this is the struct rtrs_msg_conn_req(9) page from the Kernel API Manual, and it's literally the βhey server, can we connect?β message in struct form. The client sends it, the server receives it, and the vibes are immaculate π«Ά.
β¨ SYNOPSIS β¨
struct rtrs_msg_conn_req {
u8 __cma_version;
u8 __ip_version;
__le16 magic;
__le16 version;
__le16 cid;
__le16 cid_num;
__le16 recon_cnt;
uuid_t sess_uuid;
uuid_t paths_uuid;
u8 first_conn : 1;
};
π§ Members π§
__cma_versionβ Set to0bycma.cin case ofAF_IB, and do not touch that, bestie. Seehttps://www.spinics.net/lists/linux-rdma/msg22397.htmlβ iykyk.__ip_versionβ On the sender side this should be set to0, orcma_save_ip_infowill extract garbage and fail. That's a no-cap warning, fr fr π.magicβ RTRS magic β¨versionβ RTRS protocol versioncidβ Current connection idcid_numβ Number of connections per sessionrecon_cntβ Reconnections countersess_uuidβ UUID of a session (path)paths_uuidβ UUID of a group of sessions (paths)first_connβ1if the connection request is the first for that session, otherwise0.
π NOTE π
max size56bytes, seeman rdma_connectπ. That's the whole note, and it's highkey important.
π SEE ALSO π
- Kernel file
./drivers/infiniband/ulp/rtrs/rtrs-pri.henumrtrs_msg_types(9), enumrtrs_msg_flags(9), structrtrs_sg_desc(9), structrtrs_msg_conn_rsp(9), structrtrs_msg_info_req(9), structrtrs_msg_info_rsp(9), structrtrs_msg_rkey_rsp(9), structrtrs_msg_rdma_read(9), structrtrs_msg_rdma_write(9), structrtrs_msg_rdma_hdr(9)
xoxo, your ./drivers/infiniband/ulp/rtrs bestie β October 2026 edition of struct rtrs_msg_conn_req(9), mwah π.
π¦ 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