nvme_identi...ry_ctrl_list(2)

💖 nvme_identify_secondary_ctrl_list(2) 💖

okay bestie, sit down, hydrate, because we're reading a page straight out of the libnvme API manual and it's actually kind of a banger ✨

---

✨ NAME ✨

nvme_identify_secondary_ctrl_list — retrieves secondary controller list 🎀

---

🌸 SYNOPSIS 🌸

int nvme_identify_secondary_ctrl_list (int fd , __u16 cntid , struct
nvme_secondary_ctrl_list *sc_list );

like... that's the whole vibe. three little inputs, one int coming back at you 💅

---

🦋 ARGUMENTS 🦋

• fd — file descriptor of nvme device. it's giving "your ticket into the device", no cap 🎟️
• cntid — return controllers starting at this identifier. so like, the starting line. everybody at or after this point, come on down 🫶
• sc_list — user space destination address to transfer the data. this is where the tea gets delivered 📬

---

👑 DESCRIPTION 👑

so here's the situation, bestie. a Secondary Controller List gets returned to the host, and it covers up to 127 secondary controllers that are associated with the primary controller processing this command. iconic capacity fr fr 🌈

the list contains entries for controller identifiers that are greater than or equal to the value you specified in the Controller Identifier (cntid). so it's not "exactly this one", it's "this one and everyone after" — the way that it's a whole squad, not a solo act 💀

see struct nvme_secondary_ctrls_list for a definition of the returned structure. go look, it's right there 👀

---

⭐ RETURN ⭐

the nvme command status if a response was received (see enum nvme_status_field), or -1 with errno set otherwise 😭

so like: either you get the status back and everything's chill, or you get -1 and errno is out here snitching about what went wrong. respect the snitch 🫡

---

and that's the page, bestie!! written by the libnvme girlies, dated July 2026, and living in the libnvme API manual forever 💜 mwah, go identify some secondary controllers, you absolute icon 🧚‍♀️💖