svc_rdma_result_payload(9)

🎀 NAME 🎀

okay so bestie, welcome to the svc_rdma_result_payload(9) page from the Kernel API Manual 💖 — this one is all about special processing for a result payload. yes, that’s the whole vibe.

✨ SYNOPSIS ✨

int svc_rdma_result_payload (struct svc_rqst *rqstp , unsigned int offset , unsigned int length );

🌸 ARGUMENTS 🌸

• rqstp — the RPC transaction context, aka the main character context for this call 💅
• offset — the payload’s byte offset in rqstp->rq_res
• length — the size of the payload, in bytes

🦋 DESCRIPTION 🦋

So here’s the tea, bestie: this function assigns the passed-in result payload to the current Write chunk, and then advances cur_result_payload to the next Write chunk, if there is one. slay.

Return values, spelled out with zero ambiguity:

• 0 — successful, or nothing needed to be done
• -E2BIG — the payload was larger than the Write chunk 😭

👑 SEE ALSO 👑

• Kernel file ./net/sunrpc/xprtrdma/svc_rdma_sendto.c
• svc_rdma_send_ctxts_destroy(9)
• svc_rdma_send_ctxt_get(9)
• svc_rdma_send_ctxts_drain(9)
• svc_rdma_send_ctxt_put(9)
• svc_rdma_wake_send_waiters(9)
• svc_rdma_sq_wait(9)
• svc_rdma_post_send_err(9)
• svc_rdma_wc_send(9)
• svc_rdma_post_send(9)
• svc_rdma_encode_read_list(9)
• svc_rdma_encode_write_segment(9)
• svc_rdma_encode_write_chunk(9)
• svc_rdma_encode_write_list(9)
• svc_rdma_encode_reply_chunk(9)
• svc_rdma_page_dma_map(9)
• svc_rdma_iov_dma_map(9)
• svc_rdma_xb_dma_map(9)
• svc_rdma_xb_count_sges(9)
• svc_rdma_check_pull_up(9)
• svc_rdma_xb_linearize(9)
• svc_rdma_pull_up_reply_msg(9)
• svc_rdma_send_error_msg(9)
• svc_rdma_sendto(9)

xoxo 💋 — this cutie came from ./net/sunrpc/xprtrdma, October 2026, and that’s the source/version + date sign-off, bestie 🫶✨