nvme_get_lo...rted_effects(2)

💖 nvme_get_log_mi_cmd_supported_effects — libnvme API manual, section 2 🦋

okay bestie, sit DOWN, because we're doing a manpage and it's actually gonna be fun. this one lives in the libnvme API manual, section 2, and yes the title up top is all nvme_get_lo...rted_effects(2) because apparently even the header needed a lil trim 🙈. anyway, it's giving "let me peek at what MI commands this controller can actually do" energy and we're obsessed.

---

✨ NAME ✨

nvme_get_log_mi_cmd_supported_effects — displays the MI Commands Supported by the controller 💅

like. it literally shows you the MI commands your controller supports. no cap, that's the whole job.

---

🎀 SYNOPSIS 🎀

int nvme_get_log_mi_cmd_supported_effects (int fd , bool rae , struct
nvme_mi_cmd_supported_effects_log *log );

three args, returns an int, absolute main character energy. let's break it down 🫶

---

🌸 ARGUMENTS 🌸

• fd — the file descriptor of the nvme device. it's the lil handle telling us which device we're talking to ✨
• rae — retain asynchronous events. a bool, so it's a yes/no vibe check on whether we're holding onto those async events or not 💜
• log — the MI Command Supported and Effects data structure. this is where the good stuff gets written, a struct nvme_mi_cmd_supported_effects_log * no less 👑

---

🌈 RETURN 🌈

here's the tea: you get back the nvme command status if a response was actually received — and like, go look at enum nvme_status_field for the deets on those. ORRR you get -1 and errno is set instead 😭

fr fr, if you see -1, check errno. that's your sign, bestie. don't ignore it 💀

---

and that's the whole page, iconic behavior honestly. this gem comes to you from the libnvme API manual and it's dated July 2026 — so yes, it's serving future-forward and also literally just July 2026, which is a whole mood ⭐💖 slay, go read your logs. periodt. 🌟