rpc_clnt_add_xprt(9)

💅 rpc_clnt_add_xprt(9) — Kernel API Manual ✨

Okay bestie, welcome to the group chat for the kernel’s transport-adding era. This is the rpc_clnt_add_xprt(9) page, and yes it’s giving “add a new transport to a rpc_clnt” main character energy. 🎀

🌸 NAME 🌸

rpc_clnt_add_xprt — Add a new transport to a rpc_clnt 💖

✨ SYNOPSIS ✨

int rpc_clnt_add_xprt (struct rpc_clnt *clnt , struct xprt_create
       *xprtargs , int (*setup)(struct rpc_clnt *, struct rpc_xprt_switch *,
       struct rpc_xprt *, void *) , void *data );

🎀 ARGUMENTS 🎀

• clnt — pointer to struct rpc_clnt; this is the client bestie getting a new transport.
• xprtargs — pointer to struct xprt_create; the transport creation info lives here.
• setup — callback to test and/or set up the connection. Very “you got this” energy.
• data — pointer to setup function data; the little bag of stuff passed along to the setup callback.

🦋 DESCRIPTION 🦋

So here’s the vibe: it creates a new transport using the parameters set in args and adds it to clnt. 💫

If ping is set, then test that connectivity succeeds before adding the new transport. No cap, that’s the flow.

💜 SEE ALSO 💜

This one lives in the kernel file ./net/sunrpc/clnt.c, and the whole SEE ALSO squad is:

• rpc_create(9)
• rpc_clone_client(9)
• rpc_clone_client_set_auth(9)
• rpc_switch_client_transport(9)
• rpc_clnt_iterate_for_each_xprt(9)
• rpc_cancel_tasks(9)
• rpc_hold_client(9)
• rpc_release_client(9)
• rpc_bind_new_program(9)
• rpc_run_task(9)
• rpc_call_sync(9)
• rpc_call_async(9)
• rpc_run_bc_task(9)
• rpc_prepare_reply_pages(9)
• rpc_peeraddr(9)
• rpc_peeraddr2str(9)
• rpc_localaddr(9)
• rpc_net_ns(9)
• rpc_max_payload(9)
• rpc_max_bc_payload(9)
• rpc_force_rebind(9)
• rpc_clnt_test_and_add_xprt(9)
• rpc_clnt_setup_test_and_add_xprt(9)

xoxo, your kernel bestie 💖 — sourced from ./net/sunrpc, dated October 2026, and filed under rpc_clnt_add_xprt(9) 🫶✨