svc_send(9)

💌 svc_send(9) — bestie's guide to the Kernel API Manual 💌

okay so imagine you're deep in the Kernel API Manual and you just found svc_send(9)... hi, hello, welcome, this one's short and sweet and honestly kind of iconic 💅

---

🌸 NAME 🌸

svc_send — literally just: Return reply to client 🫶 that's the whole vibe. you send the reply. the client gets it. slay.

---

✨ SYNOPSIS ✨

void svc_send (struct svc_rqst *rqstp );

no cap, that's the exact signature — returns void, takes one pointer named rqstp, and there is a lil space before the closing paren, we keep it exactly as written, periodt 💖

---

🎀 ARGUMENTS 🎀

• rqstp — the RPC transaction context 💫 that's your whole situation right there, it's giving "everything you need to know about the request in flight". hand it over and the reply goes out.

---

🦋 SEE ALSO 🦋

the girlies in the Kernel file ./net/sunrpc/svc_xprt.c squad, all linked up and ready for your reading list 👑:

• svc_reg_xprt_class(9)
• svc_unreg_xprt_class(9)
• svc_print_xprts(9)
• svc_xprt_deferred_close(9)
• svc_xprt_received(9)
• svc_xprt_create_from_sa(9)
• svc_xprt_create(9)
• svc_print_addr(9)
• svc_xprt_enqueue(9)
• svc_reserve(9)
• svc_wake_up(9)
• svc_recv(9)
• svc_xprt_close(9)
• svc_xprt_destroy_all(9)
• svc_find_listener(9)
• svc_find_xprt(9)
• svc_xprt_names(9)

---

🌈 friendly reminder: every one of those names is copied character-for-character, because we do not play with manpage accuracy in this house 🔥

k bye, ily, go read the xprt source bestie 😭🫶

— sourced fresh from ./net/sunrpc, dated October 2026, still reppin' svc_send(9) ⭐💜🧚