mpi3mr_queu...uction_event(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

mpi3mr_queue_qd_reduction_event — okay so this one queues up a TG QD reduction event, and yes bestie that's exactly as iconic as it sounds 🎀

Quick vibe check first: this page lives in the Kernel API Manual, section 9, and the whole thing is filed under ./drivers/scsi/mpi3mr 🌸

✨ SYNOPSIS ✨

void mpi3mr_queue_qd_reduction_event (struct mpi3mr_ioc *mrioc , struct
mpi3mr_throttle_group_info *tg );

Like, it returns nothing and takes two pointers. Simple. Clean. Main character energy 👑

🫶 ARGUMENTS 🫶

  • mrioc — the adapter instance reference, aka the whole controller's whole deal 💅
  • tg — the throttle group information pointer, aka the TG in question 🦋

🌈 DESCRIPTION 🌈

So this function is an accessor — no cap, that's the actual word — and what it does is queue up one synthetically generated driver event onto the event worker thread ✨

And what's that event for? It gets used to reduce the QD of all the VDs in the TG, and that reduction happens from the worker thread, not right here, not right now 🧚

It's giving "I'll schedule it, you go handle it." Obsessed with the delegation tbh 💜

⭐ RETURN ⭐

None. Literally nothing. Void core. We love a low-maintenance return value 🎀

👑 SEE ALSO 👑

The kernel file it all lives in: ./drivers/scsi/mpi3mr/mpi3mr_os.c 🌸

And now the full friend group, no one left out:

That's the whole page bestie, every single flag-adjacent friend accounted for, iykyk 💅

And finally the send-off: this gem comes from ./drivers/scsi/mpi3mr, stamped October 2026, and it's mpi3mr_queu...uction_event(9) all day every day. Periodt. 🦋💖

📦 where this page comes from