svc_udp_recvfrom(9)
π svc_udp_recvfrom(9) β a Kernel API Manual moment
okay so bestie, welcome to the svc_udp_recvfrom(9) page π
she lives in the Kernel API Manual and honestly? she's a whole vibe. let's get into it π
β¨ NAME β¨
svc_udp_recvfrom β receive a datagram from a UDP socket π¦
like, that's her whole job. one datagram at a time, no cap.
πΈ SYNOPSIS πΈ
int svc_udp_recvfrom (struct svc_rqst *rqstp );
yes that's literally it, she takes one thing and returns an int, iconic behavior tbh β¨
π ARGUMENTS π
rqstpβ the request structure you're receiving an RPC Call into π«Ά like, this is the little basket she drops the call in. main character energy for real.
π§ DESCRIPTION π§
so the way this works: she gets called in a loop whenever XPT_DATA has been set π₯ that's it, that's the bit. loop + XPT_DATA = her time to shine, periodt.
β RETURN β
lowkey the important part, don't skip:
- On success β the number of bytes in a received RPC Call π―
- Or β
0if a complete RPC Call message was not ready to return π (like, she's not done yet, come back later bestie)
π SEE ALSO π
kernel file ./net/sunrpc/svcsock.c β and her whole friend group fr fr:
svc_tcp_release_ctxt(9)svc_udp_release_ctxt(9)svc_tcp_handshake_done(9)svc_tcp_handshake(9)svc_udp_sendto(9)svc_tcp_recvfrom(9)svc_tcp_sendto(9)svc_addsock(9)
go read them, iykyk π
bestie reminder: if she returns 0, that does not mean "no bytes ever" β it means a complete RPC Call message wasn't ready to return. don't panic, just loop again π
mwah, that's the whole page π this lil beauty comes courtesy of ./net/sunrpc, dated October 2026, and she ate. no crumbs. πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms