idpf_send_mb_msg_kfree(9)

📦 version 7.3.1, in nixpkgs unstable

💖 idpf_send_mb_msg_kfree(9) 💖

okay bestie, welcome to the Kernel API Manual entry for idpf_send_mb_msg_kfree(9) — yes, the manual name is literally Kernel API Manual, and we’re about to make it make sense. no cap ✨

🌸 NAME 🌸

idpf_send_mb_msg_kfree — send mailbox message and free the send buffer. that’s the whole vibe: it sends the mailbox message, then frees the send buffer. tidy queen behavior, we love to see it 🧚💅

✨ SYNOPSIS ✨

the signature is giving:

int idpf_send_mb_msg_kfree (struct idpf_adapter *adapter , struct
       libie_ctlq_xn_send_params *xn_params , void *send_buf , size_t
       send_buf_size );

🎀 ARGUMENTS 🎀

  • adapter — driver specific private structure. it’s the driver’s own private little context blob, lowkey essential 🫶
  • xn_params — Xn send parameters to fill. bestie, you’re filling these in, so pay attention ✨
  • send_buf — buffer to send, can be released with kfree. yes, the free is literally part of the function’s main character energy 💖
  • send_buf_size — size of the send buffer. gotta know how big the buffer is, obviously 🎀

🦋 DESCRIPTION 🦋

so here’s the tea: libie_cp functions consume only buffers above certain size, smaller buffers are assumed to be on the stack. however, for some commands with variable message size it makes sense to always use kzalloc, which means we have to free smaller buffers ourselves. and that’s exactly the little cleanup moment this function is handling, periodt 🧚✨

💅 RETURN 💅

returns 0 if no unexpected errors were encountered, negative error code otherwise. slay when it’s 0, sad little negative number when it’s not 😭💀

👑 SEE ALSO 👑

Kernel file ./drivers/net/ethernet/intel/idpf/idpf_virtchnl.c — go read it, bestie, it’s right there 👀

and that’s the page, bestie 🫶 this little icon lives in ./drivers/net/ethernet/intel/idpf, dated October 2026, and it’s the idpf_send_mb_msg_kfree(9) manual page. go off 💅🌈

📦 where this page comes from