rpcrdma_inline_fixup(9)

okay so bestie, welcome to the rpcrdma_inline_fixup(9) page from the Kernel API Manual 💖 this is the one that scatters inline received data into rqst's iovecs, and it's iconic ✨

🌸 NAME 🌸

rpcrdma_inline_fixup — Scatter inline received data into rqst's iovecs 🎀

✨ SYNOPSIS ✨

unsigned long rpcrdma_inline_fixup (struct rpc_rqst *rqst , char *srcp ,
       int copy_len , int pad );

🎀 ARGUMENTS 🎀

• rqst — the controlling RPC request, aka the main character here 👑
• srcp — points to the RPC message payload in the receive buffer, periodt 💅
• copy_len — the remaining length of receive buffer content, fr fr
• pad — the Write chunk pad bytes needed; it's zero for pure inline 🌸

🦋 DESCRIPTION 🦋

The upper layer has <highkey>already</highkey> set the maximum number of bytes it can receive in each component of rq_rcv_buf, bestie. Those values are set in the head.iov_len, page_len, tail.iov_len, and buflen fields. ✨

Unlike the TCP equivalent (xdr_partial_copy_from_skb), in many cases this function simply updates iov_base pointers in rq_rcv_buf to point directly to the received reply data, to avoid copying reply data. No cap, it's giving "point straight at the data" energy 😭💖

It returns the count of bytes which had to be memcopied. That's the whole mood 🫶

🌈 SEE ALSO 🌈

Kernel file: ./net/sunrpc/xprtrdma/rpc_rdma.c 📁

• rpcrdma_set_max_header_sizes(9)
• rpcrdma_sendctx_unmap(9)
• rpcrdma_prepare_send_sges(9)
• rpcrdma_marshal_req(9)
• rpcrdma_reset_cwnd(9)
• rpcrdma_unpin_rqst(9)
• rpcrdma_complete_rqst(9)
• rpcrdma_reply_handler(9)

xoxo, this page's source/version is ./net/sunrpc/xprtrdma, dated October 2026 — go be iconic with your inline data, bestie 💅🫶🌸