nvme_mi_admin_identify(2)

💖 NAME 💖

nvme_mi_admin_identify — bestie, this one runs an Admin identify command and it is literally the moment your controller introduces itself ✨

This page lives in the libnvme API manual and it's giving very much "official docs but make it fun" 💅

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_identify (nvme_mi_ctrl_t ctrl , struct
nvme_identify_args *args );

okay so look at that signature, it's so clean 😭 two params, one int coming back at you 🫶

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller that's gonna process this identify command. this is your girl, she's doing the work 💪
• args — the Identify command arguments. all the lil settings for the ask live in here 🍓

---

🦋 DESCRIPTION 🦋

So here's the tea: you're performing an Identify command, and you're doing it using the Identify command parameters tucked inside args 🎯

It stores the identify data in ->data, and (if it's set) it drops the result from cdw0 into args->result. lowkey such a thoughtful lil detail, putting everything where you'd expect 💖

⚠️ heads up bestie: it will return an error if the length of the response data (from the controller) is not a full NVME_IDENTIFY_DATA_SIZE. no partial readings here, we accept nothing less than the whole thing, periodt 💀

Also, go peep: struct nvme_identify_args — that's where all the args lore lives 👑

---

⭐ RETURN ⭐

It hands you back the nvme command status if a response was received (check enum nvme_status_field for that), or -1 with errno set otherwise 🌈

so like… either you get a real status, or you get -1 and errno tells you what went down. iykyk 🙈

---

that's the whole page, you ate it, no crumbs, fr fr 👑

sign-off szn 🎀 this was the libnvme API manual, July 2026 edition — written with love, shipped with vibes, and yes the nvme_mi_admin_identify name shows up twice up top because that's just how manpages do 💅✨