rtrs_clt_init_req(9)

Hi bestie 💖 this is rtrs_clt_init_req(9) from the Kernel API Manual, and it's giving “initialize the request that tracks an inflight IO” main character energy. No cap. 🫶

✨ NAME ✨

rtrs_clt_init_req — initialize an rtrs_clt_io_req holding information about an inflight IO. The user buffer holding user control message (not data) is copied into the corresponding buffer of rtrs_iu (req->iu->buf), which later on will also hold the control message of rtrs. 🎀

🌈 SYNOPSIS 🌈

void rtrs_clt_init_req (struct rtrs_clt_io_req *req , struct rtrs_clt_path *clt_path , void (*conf)(void *priv, int errno) , struct rtrs_permit *permit , void *priv , const struct kvec *vec , size_t usr_len , struct scatterlist *sg , size_t sg_cnt , size_t data_len , int dir );

🦋 ARGUMENTS 🦋

• req — an io request holding information about IO.
• clt_path — client path.
• conf — conformation callback function to notify upper layer.
• permit — permit for allocation of RDMA remote buffer.
• priv — private pointer.
• vec — kernel vector containing control message.
• usr_len — length of the user message.
• sg — scater list for IO data.
• sg_cnt — number of scater list entries.
• data_len — length of the IO data.
• dir — direction of the IO.

💜 SEE ALSO 💜

• Kernel file ./drivers/infiniband/ulp/rtrs/rtrs-clt.c — go look at the source, bestie 👀
• rtrs_clt_get_permit(9)
• rtrs_clt_put_permit(9)
• rtrs_permit_to_clt_con(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_failover_req(9)
• init_path(9)
• rtrs_clt_open(9)
• rtrs_clt_close(9)
• rtrs_clt_request(9)
• rtrs_clt_query(9)

Okay that's the whole page, bestie 🎀 — cute sign-off time: this rtrs_clt_init_req(9) page comes from the source line ./drivers/infiniband/ulp/rtrs and is dated October 2026. Slay. 💅✨