nvme_mi_adm..._cmd_effects(2)

💖 NAME 💖

nvme_mi_admin_get_log_cmd_effects — bestie, this is the one that goes and gets you the nvme command effects log ✨ it's a libnvme API manual page and we're keeping it cute but keeping it correct, no cap 💅

---

🎀 SYNOPSIS 🎀

int nvme_mi_admin_get_log_cmd_effects (nvme_mi_ctrl_t ctrl , enum
nvme_csi csi , struct nvme_cmd_effects_log *effects_log );

---

🦋 ARGUMENTS 🦋

• ctrl — the Controller you're querying, like the one you're sliding into the DMs of 🫶
• csi — the Command Set Identifier, iykyk
• effects_log — a User address where the effects log gets stored, aka the lil spot in memory that's holding the receipts 💾

---

✨ DESCRIPTION ✨

Okay so listen. This log page is literally describing the commands that the controller supports and the effects those commands have on the state of the NVM subsystem. Like, not just "hey these commands exist" — it's also telling you what each one does to the NVM subsystem's whole vibe. It's giving full transparency 👑

---

🌸 RETURN 🌸

You get the nvme command status if a response was received (go check enum nvme_status_field for what the numbers mean, bestie). If you got literally nothing back? You get -1 with errno set instead 😭 so always peek at errno, fr fr.

no response = no vibes = -1 plus errno. don't skip the errno check, that's the whole point 💀

---

and that's the whole page, slay 💜 stay iconic, keep your errno close, and remember — this came to you from the libnvme API manual, dated July 2026 ✨🎀🦋