xdr_decode_read_segment(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– xdr_decode_read_segment(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for xdr_decode_read_segment(9) β€” manual name folded in, header line not copied, we're being efficient πŸ’…. This one is literally about decoding the contents of a Read segment, and yes it's giving kernel-internals main character energy.


✨ NAME ✨

xdr_decode_read_segment β€” Decode contents of a Read segment


🌸 SYNOPSIS 🌸

__be32 * xdr_decode_read_segment (__be32 *p , u32 *position , u32 *handle , u32 *length , u64 *offset );

πŸŽ€ ARGUMENTS πŸŽ€

  • p β€” Pointer to the undecoded Read segment 🫢
  • position β€” Upon return, the segment's position
  • handle β€” Upon return, the RDMA handle
  • length β€” Upon return, the RDMA length
  • offset β€” Upon return, the RDMA offset

no cap, every one of those "upon return" ones is an output situation β€” the call fills them in when it comes back ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

Return value: Pointer to the XDR item that follows the Read segment. That's it, that's the vibe β€” the function hands you back the pointer to the next XDR item after the Read segment πŸ’–


🌈 SEE ALSO 🌈


mwah πŸ’‹ signing off from the source/version spot ./include/linux/sunrpc, dated October 2026, still on the xdr_decode_read_segment(9) page 🫢✨

πŸ“¦ where this page comes from