svc_rdma_en...rite_segment(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… svc_rdma_encode_write_segment(9) β€” like, the Kernel API Manual entry bestie πŸ’…

okay so this is svc_rdma_encode_write_segment, straight out of the Kernel API Manual, and it's genuinely just doing one little job for you: encoding one Write segment. that's it. that's the whole vibe. ✨


🌸 NAME 🌸

svc_rdma_encode_write_segment β€” Encode one Write segment πŸŽ€


✨ SYNOPSIS ✨

ssize_t svc_rdma_encode_write_segment (struct svc_rdma_send_ctxt *sctxt
, const struct svc_rdma_chunk *chunk , u32 *remaining , unsigned int
segno );

no cap, that's the whole signature. copy it exactly, don't @ me 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

okay bestie let's meet the cast, they all have main character energy in their own way:

  • sctxt β€” the send context for the RPC Reply. she's the stage the whole thing happens on πŸ’–
  • chunk β€” the Write chunk you're pushing. yes, this one. go off πŸ‘‘
  • remaining β€” the remaining bytes of the payload left in the Write chunk. it's giving "how much room is left in the suitcase" 🧳
  • segno β€” which segment in the chunk. like, which one are we doing rn, bestie 🌈

πŸ”₯ DESCRIPTION πŸ”₯

so here's the return-value tea, and it's short and sweet:

  • On success it returns the length in bytes of the Reply XDR buffer that was consumed by the Write segment β€” and it updates remaining. slay, it's doing two things πŸ’…
  • -EMSGSIZE on XDR buffer overflow. translation: you tried to put too much in there and the buffer said "absolutely not" πŸ’€
no extra lore here, that's literally the whole description. don't invent stuff. periodt.

⭐ SEE ALSO ⭐

go read the source, it's right here in the kernel file ./net/sunrpc/xprtrdma/svc_rdma_sendto.c πŸ“‚

and the whole friend group:


mwah πŸ’‹ that's the page. this little cutie lives in ./net/sunrpc/xprtrdma, and the version is dated October 2026 β€” so mark your calendars bestie, and see you in the same title slot: svc_rdma_en...rite_segment(9) πŸŽ€βœ¨

πŸ“¦ where this page comes from