libie_cp_can_send_onstack(9)

💅 libie_cp_can_send_onstack(9) — Kernel API Manual 💅

okay bestie, welcome to the Kernel API Manual page for libie_cp_can_send_onstack(9). This one is short, sweet, and honestly kind of iconic: it answers one very specific question about whether a message can be sent using a stack variable. no cap. 🫶

---

✨ NAME ✨

libie_cp_can_send_onstack — can a message be sent using a stack variable? yes, that is literally the whole assignment. 💖

---

🌸 SYNOPSIS 🌸

bool libie_cp_can_send_onstack (u32 size );

---

🎀 ARGUMENTS 🎀

• size — ctlq data buffer size. that's the vibe, that's the input. 🎀

---

🦋 RETURN 🦋

It returns true if the message size is small enough for the caller to pass an on-stack buffer, and false if kmalloc is needed. so, yes: this function is out here doing a little size vibe check for you. ✨

---

👑 SEE ALSO 👑

start at the kernel file ./include/linux/net/intel/libie/controlq.h, then follow the enum libie_ctlq_type(9) rabbit hole. the whole crew is linked up:

• enum libie_ctlq_type(9)
• struct libie_ctlq_ctx(9)
• struct libie_ctlq_reg(9)
• struct libie_cp_dma_mem(9)
• struct libie_ctlq_msg(9)
• struct libie_ctlq_create_info(9)
• struct libie_ctlq_info(9)
• struct libie_ctlq_desc(9)
• struct libie_ctlq_clean_params(9)
• libie_ctlq_release_rx_buf(9)
• enum libie_ctlq_xn_state(9)
• struct libie_ctlq_xn(9)
• struct libie_ctlq_xn_manager(9)
• struct libie_ctlq_xn_send_params(9)
• struct libie_ctlq_xn_recv_params(9)
• struct libie_ctlq_xn_init_params(9)

---

and that's the whole page, bestie. this little baddie is serving source/version ./include/linux/net/intel/libie energy, dated October 2026, and it's literally titled libie_cp_can_send_onstack(9). bye and slay 💖✨