xprt_sock_sendmsg(9)

💖 NAME 💖

Okay bestie, welcome to the Kernel API Manual page for xprt_sock_sendmsg(9) — the one where we write an xdr_buf directly to a socket, and the vibe is very kernel networking but make it cute 🌸.

✨ SYNOPSIS ✨

int xprt_sock_sendmsg (struct socket *sock , struct msghdr *msg , struct
       xdr_buf *xdr , unsigned int base , rpc_fraghdr marker , unsigned int
       *sent_p );

Okay so this is the whole call, and yes the line breaks are giving kernel source realness 😌.

🎀 ARGUMENTS 🎀

• sock — the open socket to send on 🫶.
• msg — the socket message metadata.
• xdr — the xdr_buf containing this request.
• base — the starting position in the buffer.
• marker — the stream record marker field.
• sent_p — the place where it returns the total number of bytes successfully queued for sending. Lowkey important, bestie 💖.

🦋 DESCRIPTION 🦋

Return values, because we're not leaving you guessing: on success, this returns zero and fills in sent_p ✨. And if sock is not a struct socket, it's -ENOTSOCK — that's the exact return value, no cap 😭.

Bestie, that's the whole description: success is zero plus a filled-in sent_p, and the not-a-socket case is -ENOTSOCK. Iconic, concise, we love to see it 👑.

🌈 SEE ALSO 🌈

Kernel file ./net/sunrpc/socklib.c, plus xdr_skb_read_bits(9) and csum_partial_copy_to_xdr(9) — go read those next, bestie 🫶📚.

Cute little sign-off: this page comes from source/version ./net/sunrpc, dated October 2026, and it's xprt_sock_sendmsg(9) — bye bestie, go queue those bytes 💖✨🎀