libnvme(2)

πŸ’– NAME πŸ’–

struct nvme_lm_nvme_controller_state_data β€” bestie, this is the NVMe Controller State data structure ✨ and what it does is describe the state of a NVMe Controller's I/O Submission and I/O Completion queues. That's it, that's the vibe. No cap. πŸ¦‹


✨ SYNOPSIS ✨

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];
    };
 };

πŸŽ€ Members πŸŽ€

Lowkey the whole personality of this struct is right here, so let's go member by member, no skips, periodt πŸ’…

  • hdr β€” the Header. yes queen, every good struct starts with one πŸ‘‘
  • {unnamed_union} β€” anonymous. she has no name and she doesn't need one fr fr πŸ™ˆ
  • sqs β€” the I/O Submission Queue list πŸ“
  • cqs β€” the I/O Completion Queue list 🌸

not me being obsessed with a data structure that literally just holds a header and two queue lists... and yet?? iconic. the way that hdr sits at the top like the main character and the union does its little anonymous thing underneath 🫢

okay that's the whole page bestie, you ate that πŸ’–

this was struct nvme_lm_nvme_controller_state_data from the libnvme API Manual, dated July 2026 β€” manual name libnvme(2), version libnvme(2) at the footer, and you read the entire thing top to bottom so slay πŸŒˆβ­πŸ‘‘

πŸ“¦ where this page comes from