libnvme(9)

🌸 libnvme(9) 🌸

okay bestie, welcome to the API Manual for libnvme — yes, the one and only. buckle up, this one's a struct page and it's lowkey iconic 💅

---

✨ NAME ✨

struct nvme_lm_nvme_controller_state_data — the NVMe Controller State data structure, which literally describes the state of an NVMe Controller's I/O Submission and I/O Completion queues. that's it, that's the whole vibe 🦋

---

🎀 SYNOPSIS 🎀

so here's the whole thing, exactly as it lives in the source. no cap, character for character:

struct nvme_lm_nvme_controller_state_data {
    struct nvme_lm_nvme_controller_state_data_header hdr;
    union {
      struct nvme_lm_io_submission_queue_data sqs[0];
      struct nvme_lm_io_completion_queue_data cqs[0];
      __u8 queue_data_buf[4088];
    };
 };

like, look at that anonymous union go. it's giving main character energy fr fr 🔥

---

💖 Members 💖

okay now the part where we meet the cast 🫶

• hdr — the Header. the header!! every struct needs one and this is hers 💅
• {unnamed_union} — anonymous. she has no name, she needs no name. mysterious. iconic. we stan 🙈
• sqs — the I/O Submission Queue list. that's the submissions, bestie ✨
• cqs — the I/O Completion Queue list. and that's the completions to match 🌈
• queue_data_buf — the Queue data buffer. the buffer of queue data. holding it down at 4088 bytes 🍓

---

lowkey reminder: the union is anonymous, so those three members — sqs, cqs and queue_data_buf — all hang out in the same spot. that's the whole point of a union, iykyk 💜

---

and that's the page!! go forth and read your controller state data, queen 👑

⭐ sign-off time ⭐ — this masterpiece is dated October 2026, it's all about struct nvme_lm_nvme_controller_state_data, and it comes to you straight from libnvme(9). mwah 💋🎀