rtrs_permit_to_clt_con(9)
π rtrs_permit_to_clt_con(9) β the Kernel API Manual glow-up
okay so bestie, welcome to section 9 of the kernel API manual, and today's main character is rtrs_permit_to_clt_con. yes it's a long name. yes it's worth it. let's go π«Ά
β¨ NAME β¨
rtrs_permit_to_clt_con β returns the RDMA connection pointer by the permit. that's the whole vibe, no cap π«
πΈ SYNOPSIS πΈ
struct rtrs_clt_con * rtrs_permit_to_clt_con (struct rtrs_clt_path
*clt_path , struct rtrs_permit *permit );
look at that signature. iconic. she takes two things and gives you back a struct rtrs_clt_con * π₯
π ARGUMENTS π
clt_pathβ the client path pointer. like, the path you're on, queen πpermitβ the permit for the allocation of the RDMA buffer. it's literally your permission slip for the buffer, iykyk π«
π NOTE π
okay this is the part where you pay attention, bestie, because it's giving important:
- IO connection starts from
1. 0connection is for user messages.
so like, connection zero is not for your IO, she's for user messages. don't mix them up, fr fr π
π¦ SEE ALSO π¦
the kernel file:
./drivers/infiniband/ulp/rtrs/rtrs-clt.c
and the whole friend group, all of them, every single one π«Ά:
rtrs_clt_get_permit(9)rtrs_clt_put_permit(9)rtrs_clt_change_state(9)get_next_path_rr(9)get_next_path_min_inflight(9)get_next_path_min_latency(9)rtrs_clt_init_req(9)rtrs_clt_failover_req(9)init_path(9)rtrs_clt_open(9)rtrs_clt_close(9)rtrs_clt_request(9)rtrs_clt_query(9)
go read them. all of them. that's the assignment. not me being a nerd, me being correct π
and that's the page, bestie! this one came straight out of ./drivers/infiniband/ulp/rtrs and she's dated October 2026. mwah, slay, periodt πβ¨ππ¦
π¦ 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