rpc_call_async(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ rpc_call_async(9) ✨

okay so bestie, welcome to the rpc_call_async page from the Kernel API Manual πŸ’… this is a kernel function and it does one thing and it does it asynchronously, which is basically main-character energy for syscalls β€” it does NOT wait around for the reply like some needy sync function, it just fires the call and dips πŸ¦‹


🌸 NAME 🌸

rpc_call_async β€” Perform an asynchronous RPC call πŸ”₯

like, the whole vibe is right there in the name, iykyk


πŸŽ€ SYNOPSIS πŸŽ€

int rpc_call_async (struct rpc_clnt *clnt , const struct rpc_message
*msg , int flags , const struct rpc_call_ops *tk_ops , void *data );

it gives back an int, and it takes five things β€” every single one of them is listed below, no skips, we don't do that here 🫢


πŸ’– ARGUMENTS πŸ’–

  • clnt β€” pointer to RPC client πŸ’« like, the client struct you're calling through. no client, no call, periodt.
  • msg β€” RPC call parameters ✨ the whole description of the call lives in here.
  • flags β€” RPC call flags πŸŽ€ little behaviour switches, exactly as advertised.
  • tk_ops β€” RPC call ops 🧚 the ops struct, which is where the callback situation lives (tk is giving "task", and honestly that tracks).
  • data β€” user call data πŸ’œ your own pointer, your own business, it gets handed back to you.

🌈 SEE ALSO 🌈

bestie there are SO many siblings, this page has a whole friend group πŸ‘‘

Kernel file ./net/sunrpc/clnt.c β€” that's where the actual code lives, go say hi 🫢


okay that's the page!! πŸ’€ source is ./net/sunrpc, dated October 2026, and it's rpc_call_async(9) in the Kernel API Manual β€” go be asynchronous about it, love u, bye πŸ’…πŸ’–

πŸ“¦ where this page comes from