svc_new_thread(9)

💅 svc_new_thread(9) — the kernel API manual, bestie edition 🧚

okay so you found the svc_new_thread(9) page, welcome, pull up a chair 💖 this is the whole thing, nothing skipped, i promise.

---

✨ NAME ✨

svc_new_thread — spawn a new thread in the given pool 🫶

---

🌸 SYNOPSIS 🌸

int svc_new_thread (struct svc_serv *serv , struct svc_pool *pool );

---

🎀 ARGUMENTS 🎀

• serv — the serv to which the pool belongs 👑 like, the whole operation.
• pool — pool in which thread should be spawned 🦋 the specific lil home for your new thread.

---

💜 DESCRIPTION 💜

So the vibe is: create a new thread inside pool, which is a part of serv. That's it, that's the whole errand. ✨

⚠️ real talk though — the caller must hold the service mutex. not optional, not "i'll grab it later", not "my friend is holding it". hold it. 🔒

Returns 0 on success, or -errno on failure. so like, zero means slay, negative means something went sideways and you get an errno about it 😭

---

🌈 SEE ALSO 🌈

Kernel file ./net/sunrpc/svc.c 👀 and honestly the whole friend group:

• sunrpc_get_pool_mode(9)
• svc_serv_nrpools(9)
• svc_pool_for_cpu(9)
• svc_create(9)
• svc_create_pooled(9)
• svc_pool_wake_idle_thread(9)
• svc_set_pool_threads(9)
• svc_set_num_threads(9)
• svc_serv_maxthreads(9)
• svc_rqst_replace_page(9)
• svc_rqst_release_pages(9)
• svc_exit_thread(9)
• svc_register(9)
• svc_stat_alloc_counts(9)
• svc_stat_free_counts(9)
• svc_process(9)
• svc_process_bc(9)
• svc_max_payload(9)
• svc_proc_name(9)
• svc_encode_result_payload(9)
• svc_fill_symlink_pathname(9)

---

okay that's the whole page, no cap, every single flag and reference accounted for 💅 go forth and spawn responsibly. mwah 🫶

this icon of a manpage lives in ./net/sunrpc and is stamped October 2026 — periodt, that's the sign-off bestie 🌟