svc_rdma_encode_reply_chunk(9)

📦 version 7.3.1, in nixpkgs unstable

💅 svc_rdma_encode_reply_chunk(9)

okay bestie, settle in, because this is a page from the Kernel API Manual and it's about one very specific little function. no cap, it's a niche one, but we're gonna get you fluent. 🦋

✨ NAME ✨

svc_rdma_encode_reply_chunk — literally Encode RPC Reply's Reply chunk. that's the whole gig. she encodes, she's a Reply chunk, she's iconic. 💅

✨ SYNOPSIS ✨

ssize_t svc_rdma_encode_reply_chunk (struct svc_rdma_recv_ctxt *rctxt ,
struct svc_rdma_send_ctxt *sctxt , unsigned int length );

like, look at her. three params, one return type, zero notes. 🎀

✨ ARGUMENTS ✨

  • rctxt — the Reply context, and it's holding all the info about the RPC Call. so she knows things. 👑
  • sctxt — the Send context for the RPC Reply. this is where the send energy lives.
  • length — the size in bytes of the payload in the Reply chunk. numbers, we love her. 🍓

✨ DESCRIPTION ✨

okay so here's the vibe check on return values, and this part matters, so lock in 🔥:

  • on success, it returns length in bytes of the Reply XDR buffer that was consumed by the Reply's Reply chunk — slay, she ate.
  • -EMSGSIZE on XDR buffer overflow. so if the buffer overflows, that's the error you get. 😭
  • -E2BIG if the RPC message is larger than the Reply chunk. too much! too big! she said no. 💀
ngl bestie, those three return values are the entire description here. no extra lore, no hidden options, that's the whole page. don't go looking for more, there isn't more. 🙈

✨ SEE ALSO ✨

the kernel file lives right here: ./net/sunrpc/xprtrdma/svc_rdma_sendto.c 📁

and here's the whole friend group, fr fr — every single one of them:

like, that's a whole group chat. 💜

🌸 okay that's the page!! mwah 💋 this one came from ./net/sunrpc/xprtrdma, dated October 2026, and yes the lovely lady's full name is still svc_rdma_encode_reply_chunk(9) — iykyk. go forth and encode those reply chunks, bestie. 🫶✨

📦 where this page comes from