rpc_max_payload(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rpc_max_payload(9) β€” a Kernel API Manual moment ✨

okay so bestie, we're in the kernel API manual today (that's the manual name, iykyk πŸŽ€) and the page is all about rpc_max_payload β€” and no cap, it's a tiny one, so hydrate and let's go 🧚


🌸 NAME 🌸

rpc_max_payload β€” get the maximum payload size for a transport, in bytes πŸ’– like, literally, the biggest chunk of payload a transport can carry, measured in bytes. that's the whole vibe check.


✨ SYNOPSIS ✨

size_t rpc_max_payload (struct rpc_clnt *clnt );

it's giving "one function, one argument, one size_t back" and honestly? iconic. πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • clnt β€” the RPC client you're querying πŸ” that's the one you're asking about, bestie. RPC client to query. periodt.

πŸ’œ DESCRIPTION πŸ’œ

okay so the answer depends on what kind of transport you're on, and it's a whole two-for-two situation:

  • stream transports πŸŒ€ β€” the value is one RPC record fragment (see RFC 1831), because we don't support multi-record requests yet. not yet!! like, someday maybe, but today? one fragment. that's the rule. πŸ™ˆ
  • datagram transports πŸ“¨ β€” the value is the size of an IP packet, minus the IP, UDP, and RPC header sizes. so it's the packet size after everybody's taken their cut. math, but make it networking πŸ’…

⭐ SEE ALSO ⭐

Kernel file ./net/sunrpc/clnt.c β€” go read the source if you're feeling main character energy πŸ‘‘

and then the whole friend group, fr fr:

like, that's the whole group chat 😭 and yes rpc_max_bc_payload(9) is the sibling page, they're twins but not identical, don't mix them up πŸ’€


and that's the page!! 🫢 shoutout to ./net/sunrpc for bringing us together, timestamped October 2026, still rocking the rpc_max_payload(9) name β€” slay, ate, no crumbs left πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from