svc_serv_maxpages(9)

💖 svc_serv_maxpages(9) 💖

okay bestie, we're in the Kernel API Manual and this page is literally all about svc_serv_maxpages(9). grab a strawberry 🍓 and let's go.

---

🌸 NAME 🌸

svc_serv_maxpages — maximum count of pages needed for one RPC message ✨

✨ SYNOPSIS ✨

the signature is giving exact, no cap:

unsigned long svc_serv_maxpages (const struct svc_serv *serv );

🫶 ARGUMENTS 🫶

• serv — RPC service context 💖

🌈 DESCRIPTION 🌈

Okay so this function returns a count of pages or vectors that can hold the maximum size RPC message for serv. main character behavior tbh.

Each page array can hold at most one payload plus two overhead pages (one for the RPC header, one for tail data). yes bestie, that's the whole overhead situation, periodt.

nfsd_splice_actor might need an extra page when a READ payload is not page-aligned. not me side-eyeing alignment 🙈 — it's a might, so don't come for me.

🦋 SEE ALSO 🦋

Kernel file: ./include/linux/sunrpc/svc.h 👑

• svc_thread_should_stop(9)
• svc_thread_init_status(9)
• svc_rqst_page_release(9)
• svcxdr_init_decode(9)
• svcxdr_init_encode(9)
• svcxdr_encode_opaque_pages(9)
• svcxdr_set_auth_slack(9)
• svcxdr_set_accept_stat(9)

---

xoxo, bestie 💅 source/version: ./include/linux/sunrpc, date: October 2026, and the page is svc_serv_maxpages(9) 🎀✨