rpc_clnt_test_and_add_xprt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 rpc_clnt_test_and_add_xprt(9) 🌸

okay so bestie, welcome to the Kernel API Manual page for rpc_clnt_test_and_add_xprt(9) β€” yes that's a whole mouthful, we're gonna get through it together πŸ’–


✨ NAME ✨

rpc_clnt_test_and_add_xprt β€” literally test and add a new transport to a rpc_clnt. Two jobs, one function, main character energy fr fr πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

int rpc_clnt_test_and_add_xprt (struct rpc_clnt *clnt , struct
rpc_xprt_switch *xps , struct rpc_xprt *xprt , void *in_max_connect );

like, it returns an int, and it takes four things. that's the whole vibe check 🫢


πŸŽ€ ARGUMENTS πŸŽ€

okay so here's the cast of characters, and every single one of them matters, no skipping πŸ’…

  • clnt β€” pointer to struct rpc_clnt. this is the client bestie in question 🐚
  • xps β€” pointer to struct rpc_xprt_switch, (yes there's a lil comma in the original, we keep it, we respect it πŸ™ˆ)
  • xprt β€” pointer struct rpc_xprt. the transport itself, the little guy we're testing ✨
  • in_max_connect β€” pointer to the max_connect value for the passed in xprt transport. like, the connect limit that came in with it, lowkey important πŸ”₯

πŸ’œ SEE ALSO πŸ’œ

the full squad, everybody's here, no cap. kernel file ./net/sunrpc/clnt.c plus a whole friend group:


ngl if you got here by typing the wrong thing, that's okay, we've all been there 😭 but like, go read rpc_clnt_add_xprt(9) if you wanted the plain version, iykyk πŸ’€

and that's the page bestie!! πŸŽ€ source/version situation: this whole thing lives in ./net/sunrpc, dated October 2026, and the page is rpc_clnt_test_and_add_xprt(9) β€” slay, ate, periodt πŸŒˆπŸ‘‘πŸ’–

πŸ“¦ where this page comes from