svc_rdma_xdr_decode_req(9)

💅 svc_rdma_xdr_decode_req (9) — like, the Kernel API Manual page, bestie ✨

okay so welcome to the Kernel API Manual entry for svc_rdma_xdr_decode_req, and yes we are about to decode a transport header together, no cap 🎀

---

🌸 NAME 🌸

svc_rdma_xdr_decode_req — decodes the transport header, that's literally her whole job 💅

---

✨ SYNOPSIS ✨

int svc_rdma_xdr_decode_req (struct xdr_buf *rq_arg , struct
svc_rdma_recv_ctxt *rctxt );

---

🫶 ARGUMENTS 🫶

• rq_arg — the xdr_buf holding the ingress RPC/RDMA message, aka where the message comes in 🦋
• rctxt — the state of decoding, the little vibe check of what's going on rn

---

🔥 DESCRIPTION 🔥

So on entry, xdr->head[0].iov_base points to the first byte of the RPC-over-RDMA transport header. Periodt. That's the starting line 📍

On successful exit, head[0] points to the first byte past the RPC-over-RDMA header. And for RDMA_MSG, that is the RPC message, iykyk 💖

The length of the RPC-over-RDMA header is returned. That's the whole return situation, bestie ✨

Assumptions, because we always gotta be honest about our assumptions 🥺

• The transport header is entirely contained in the head iovec. Like, entirely. No sneaky bits hiding elsewhere 💀

---

👑 SEE ALSO 👑

Kernel file ./net/sunrpc/xprtrdma/svc_rdma_recvfrom.c, plus the whole friend group:

• svc_rdma_recv_ctxts_destroy(9)
• svc_rdma_recv_ctxt_get(9)
• svc_rdma_recv_ctxt_put(9)
• svc_rdma_release_ctxt(9)
• svc_rdma_post_recvs(9)
• svc_rdma_wc_receive(9)
• svc_rdma_flush_recv_queues(9)
• xdr_count_read_segments(9)
• xdr_count_write_chunks(9)
• svc_rdma_recvfrom(9)

---

and that's the page, bestie 🧚 this one's filed under ./net/sunrpc/xprtrdma, dated October 2026, and it's the svc_rdma_xdr_decode_req(9) girlie herself signing off 💜 slay 🎀