nvme_identify_ctrl_list(2)

💖 nvme_identify_ctrl_list — libnvme API manual, bestie edition 💖

okay so. sit down. hydrate. we're doing a system call together and it's gonna be SO good.

This is nvme_identify_ctrl_list from the libnvme API manual, and no cap, it's the little function that goes and asks your NVMe device "hey bestie, who else is in the group chat?"

---

✨ NAME ✨

nvme_identify_ctrl_list — retrieves identify controller list 🎀

---

🌸 SYNOPSIS 🌸

int nvme_identify_ctrl_list (int fd , __u16 cntid , struct
nvme_ctrl_list *cntlist );

the way that signature just is the whole function. we love a clean triple-arg moment 💅

---

🦋 ARGUMENTS 🦋

• fd — file descriptor of the nvme device. it's giving "your ticket into the building," fr fr 🎟️
• cntid — the starting CNTLID to return in the list. think of it as the starting point of the roll call 👑
• cntlist — user space destination address to transfer the data. this is where the tea gets poured 🍓

---

💜 DESCRIPTION 💜

up to 2047 controller identifiers is returned, containing a controller identifier greater than or equal to the controller identifier specified in cntid. so basically: no gatekeeping, everyone whose ID is at least cntid gets an invite ✨

See struct nvme_ctrl_list for a definition of the structure returned. yes queen, go read the struct, it's right there, it's iconic 🌈

---

🔥 RETURN 🔥

• The nvme command status if a response was received (see enum nvme_status_field) — like, it answered you 🫶
• or -1 with errno set otherwise 😭

---

heads up bestie: -1 is not a vibe, it means check errno. always check errno. periodt 💀

---

that's the whole page, and honestly? she ate. written in July 2026 for the libnvme API manual — mwah, go forth and enumerate your controllers, main character 💅💖✨🌈👑