rpcrdma_complete_rqst(9)
π rpcrdma_complete_rqst(9) π
β¨ NAME β¨
okay so bestie, we're in the Kernel API Manual, and rpcrdma_complete_rqst is the function that does exactly what it says: pass completed rqst back to RPC. It's giving βrequest finished, hand it overβ energy, periodt. π«Ά
πΈ SYNOPSIS πΈ
void rpcrdma_complete_rqst (struct rpcrdma_rep *rep );
π¦ ARGUMENTS π¦
repβ RPC/RDMA Receive context. That's the receive context, bestie, keep it close. π
π« DESCRIPTION π«
Here's the vibe: it reconstructs the RPC reply and completes the transaction while rqst is still pinned. Why is that important? Because keeping rqst pinned ensures the rep, rqst, and rq_task pointers remain stable. No cap, that's the whole flex: reply reconstructed, transaction completed, pointers staying stable. π₯π
π§ 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_inline_fixup(9)rpcrdma_unpin_rqst(9)rpcrdma_reply_handler(9)
okay that's the whole page, bestie! source/version: ./net/sunrpc/xprtrdma Β· date: October 2026 Β· page: rpcrdma_complete_rqst(9) β mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms