rpmsg_get_mtu(9)

💖 rpmsg_get_mtu(9) 💖

okay so bestie, welcome to the Kernel API Manual entry for rpmsg_get_mtu — yes it's a real function, yes it's in the kernel, and yes we're gonna get through it together 🫶

---

✨ NAME ✨

rpmsg_get_mtu — get maximum transmission buffer size for sending message.

like... it tells you how much you're allowed to yeet into a message. that's the whole vibe 💅

---

🌸 SYNOPSIS 🌸

ssize_t rpmsg_get_mtu (struct rpmsg_endpoint *ept );

that's it. one argument. she's low-maintenance, she's iconic, she ate 💅✨

---

🎀 ARGUMENTS 🎀

• ept — the rpmsg endpoint. that's your little handle to the thing, the main character of this whole function ngl 🌈

---

🦋 DESCRIPTION 🦋

so what does she do? literally this: the function returns the maximum buffer size available for a single outgoing message 📤

that's it. that's the whole job. one message out, here's your size cap. no cap 🔥

---

⭐ RETURN ⭐

• the maximum transmission size on success 🎉
• and an appropriate error value on failure 😭 (yeah, it can fail, keep an eye on it)

---

👑 SEE ALSO 👑

Kernel file ./drivers/rpmsg/rpmsg_core.c — go read the source bestie, it's right there 🧚

and the whole friend group:

• rpmsg_create_channel(9)
• rpmsg_release_channel(9)
• rpmsg_create_ept(9)
• rpmsg_destroy_ept(9)
• rpmsg_send(9)
• rpmsg_sendto(9)
• rpmsg_trysend(9)
• rpmsg_trysendto(9)
• rpmsg_poll(9)
• rpmsg_set_flow_control(9)
• __register_rpmsg_driver(9)
• unregister_rpmsg_driver(9)

---

fr fr though — if you're sending stuff over rpmsg, check your MTU first. asking forgiveness instead of permission is not the move here 🙈

---

and that's a wrap, bestie!! 💜 this little beauty lives in ./drivers/rpmsg, she's dated October 2026, and she goes by rpmsg_get_mtu(9). mwah 💋🎀🌸