libnvme(2)

💖 libnvme(2) — the API manual, bestie edition 💖

okay so picture this: you're deep in libnvme, section 2 of the manual, and you've just met struct nvme_ctrl_list</p> — the little data structure that's basically a guest list for a controller party 🎀. Let's get into it, no cap.

---

✨ NAME ✨

struct nvme_ctrl_list — Controller List 👑

🌸 SYNOPSIS 🌸

she's small, she's typed, she's here:

struct nvme_ctrl_list {
    __le16 num;
    __le16 identifier[NVME_ID_CTRL_LIST_MAX];
 };

note the exact fields, bestie — __le16 means little-endian 16-bit, and NVME_ID_CTRL_LIST_MAX is the cap on how many identifiers can fit. do not freestyle this.

🦋 Members 🦋

• num — Number of Identifiers 💅 so like, how many controller identifiers are actually in the list. the count. the headcount. the vibe check of "how many of y'all showed up".
• identifier — NVM subsystem unique controller identifier 🌟 this is the array itself, and each entry is the unique controller identifier within the NVM subsystem. it's giving roster energy — one slot per controller, up to NVME_ID_CTRL_LIST_MAX of them.

---

⚠️ real talk: identifier is a fixed-size array of NVME_ID_CTRL_LIST_MAX entries, so the struct is literally that size no matter what num says. num tells you how many are valid. don't go reading past it, that's a one-way ticket to undefined-behaviour city 💀

---

and that's the whole page, bestie — short, sweet, iconic 🌈 this was libnvme(2), page struct nvme_ctrl_list, manual section 2, from libnvme, and the page is dated July 2026 🫶 mwah, go write some good NVMe code, periodt 💜✨