rpcrdma_prepare_send_sges(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rpcrdma_prepare_send_sges(9) πŸ’…

okay bestie, welcome to the Kernel API Manual β€” yes, we're in the kernel today, put your big-girl hat on, it's giving ✨serious business✨ but make it cute.


🌸 NAME 🌸

rpcrdma_prepare_send_sges β€” the function that constructs SGEs for a Send WR. that's it, that's the whole vibe. it builds scatter/gather entries so your Send work request can actually go somewhere πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int rpcrdma_prepare_send_sges (struct rpcrdma_xprt *r_xprt , struct
       rpcrdma_req *req , u32 hdrlen , struct xdr_buf *xdr , enum
       rpcrdma_chunktype rtype );

like, five arguments, one int coming back. she's compact, she's iconic, she's lowkey doing a lot πŸ’…


πŸ’– ARGUMENTS πŸ’–

  • r_xprt β€” the controlling transport. think of it as the main character of this whole operation πŸ‘‘
  • req β€” the context of the RPC Call being marshalled. this is where the actual Call lives while it's getting its act together 🫢
  • hdrlen β€” size of the transport header, in bytes. yes bestie, bytes, we count in bytes here πŸ”’
  • xdr β€” the xdr_buf containing the RPC Call. the payload's home address fr fr 🏠
  • rtype β€” the chunk type being encoded. which flavor of chunk are we dealing with, iykyk 🌈

✨ DESCRIPTION ✨

Returns 0 on success; otherwise a negative errno is returned.

that's the whole deal, no cap. zero means slay πŸ’š, negative errno means something went off and you gotta go read the errno like it's a text from your situationship 😭

ngl there is truly not a lot of prose here β€” the details are all up in ARGUMENTS. read those, they ate.

πŸŽ€ SEE ALSO πŸŽ€


and that's the page, bestie 🧚 this one came to you from ./net/sunrpc/xprtrdma, dated October 2026 β€” a whole little time capsule of kernel lore. go forth and prepare those SGEs, you've got this πŸ’œπŸ”₯

πŸ“¦ where this page comes from