srpt_mad_recv_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… srpt_mad_recv_handler(9) β€” the MAD reception callback πŸŽ€

okay so bestie, welcome to the Kernel API Manual entry for srpt_mad_recv_handler β€” yes it's a (9) page, yes it's kernel-internals territory, and yes you're gonna slay it. this is the callback that fires when a MAD shows up. that's it, that's the vibe ✨


🌸 NAME 🌸

srpt_mad_recv_handler β€” the MAD reception callback function, aka the little function that gets pinged when someone slides a MAD into your inbox πŸ’Œ


πŸ¦‹ SYNOPSIS πŸ¦‹

void srpt_mad_recv_handler (struct ib_mad_agent *mad_agent , struct
       ib_mad_send_buf *send_buf , struct ib_mad_recv_wc *mad_wc );

so it returns void (no receipts, no return value, she just does the thing) and it takes three args. three! a whole trio. let's meet them πŸ‘‡


πŸ’– ARGUMENTS πŸ’–

  • mad_agent β€” this is the return value of ib_register_mad_agent. yes, literally the thing that function handed back to you. hand it right back here, that's the whole gig 🫢
  • send_buf β€” not used. that's it. not used. she's invited to the party but she's not dancing πŸ™ˆ
  • mad_wc β€” the work completion reporting that a MAD has been received. this is the actual "omg something arrived" notification, the main character of the parameter list πŸ‘‘

✨ SEE ALSO ✨

bestie there are like a MILLION siblings here and we're listing every single one because no one gets left behind πŸ’œ

ngl that's a whole friend group and you should absolutely go say hi to all of them. iykyk πŸ’…

πŸŽ€ signing off πŸŽ€

this page lives with the good people at ./drivers/infiniband/ulp/srpt, and it was stamped October 2026 β€” so yeah, future-dated and thriving ⭐ periodt. go forth, receive your MADs, and remember: send_buf is not used πŸ’€πŸ’–

πŸ“¦ where this page comes from