rpc_max_bc_payload(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so bestie, welcome to the Kernel API Manual entry for rpc_max_bc_payload(9). yes the manual name is literally in the title, i'm not being extra, that's just how these pages roll πŸŽ€


✨ NAME ✨

rpc_max_bc_payload β€” Get maximum backchannel payload size, in bytes πŸ’–

like, it tells you how big the backchannel payload can get. in bytes. that's the whole vibe check. πŸ¦‹


🌸 SYNOPSIS 🌸

size_t rpc_max_bc_payload (struct rpc_clnt *clnt );

that's it. one function, one argument, one size_t coming back at you. she's lowkey iconic for being this simple ✨


🫢 ARGUMENTS 🫢

  • clnt β€” RPC client to query πŸ‘‘ this is the client you're asking. you hand her over, she gets queried. simple as that.

πŸ¦‹ SEE ALSO πŸ¦‹

okay this is the part where the page just dumps the whole friend group on you 😭 but honestly? respect. they're all hanging out in the kernel file ./net/sunrpc/clnt.c and here's the full roster, no cap:

twenty-three besties. twenty-three!! literally a whole group chat πŸ’€πŸ’…


and that's the page, babe. no bugs section, no warnings, no drama β€” she's short and she knows it 🌈

ngl if you were looking for a plot twist, this is not that page. it just returns the max backchannel payload size in bytes and goes home. periodt. πŸ™ˆ

mwah πŸ’‹ this has been rpc_max_bc_payload(9) from the ./net/sunrpc corner of the universe, dated October 2026 β€” stay slay, stay sized, and remember: it's giving bytes πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from