STRUCT RTRS_MSG_RDMA_READ(9)

💖 struct rtrs_msg_rdma_read(9) 💖

okay bestie, welcome to the Kernel API Manual entry for struct rtrs_msg_rdma_read — literally the RDMA data transfer request that comes from the client 🫶 no cap, that's the whole vibe of this struct.

---

✨ NAME ✨

struct rtrs_msg_rdma_read — the RDMA data transfer request from the client, periodt 💅

---

🌸 SYNOPSIS 🌸

here's the whole glow-up, bestie — write it exactly like this:

struct rtrs_msg_rdma_read {
    __le16 type;
    __le16 usr_len;
    __le16 flags;
    __le16 sg_cnt;
    struct rtrs_sg_desc    desc[];
 };

look at that little icon 😭 four __le16s and a flexible array, and it's doing the most.

---

🦋 Members 🦋

• type — this one's always RTRS_MSG_READ, every single time, no exceptions, it's giving main character energy that never changes 💀
• usr_len — the length of the user payload, i.e. how much user stuff is in here 👑
• flags — the RTRS message flags, which is an enum rtrs_msg_flags situation, iykyk ✨
• sg_cnt — how many desc entries there are, like a headcount for the descriptor squad 🎀
• desc — the RDMA buffers where the server can write the result to 🐝 these are the spots the server is allowed to drop the results into, and honestly they're slaying

---

🔥 SEE ALSO 🔥

go look at the kernel file ./drivers/infiniband/ulp/rtrs/rtrs-pri.h — that's where the enum lives, bestie, that's the source of truth 💜

and the whole friend group is here too:

• rtrs_msg_types(9)
• enum rtrs_msg_flags(9)
• struct rtrs_sg_desc(9)
• struct rtrs_msg_conn_req(9)
• struct rtrs_msg_conn_rsp(9)
• struct rtrs_msg_info_req(9)
• struct rtrs_msg_info_rsp(9)
• struct rtrs_msg_rkey_rsp(9)
• struct rtrs_msg_rdma_write(9)
• struct rtrs_msg_rdma_hdr(9)

---

fr fr, that entire list is your reading list. don't skip it 🙈

---

and that's the page, bestie 🎀 sign-off time: this one comes from ./drivers/infiniband/ulp/rtrs, dated October 2026, and yes the page is literally called struct rtrs_msg_rdma_read(9) — we love a self-titled icon ⭐💅