libnvme(2)

💖 libnvme(2) — the struct that tells you how your admin command went 💖

okay bestie, sit down, we're doing an nvme_mi_admin_resp_hdr deep dive and honestly? it's giving foundational. this is from the libnvme manual, section 2, and it is exactly as iconic as it sounds.

---

✨ NAME ✨

struct nvme_mi_admin_resp_hdr — the Admin command response header. that's it. that's the whole vibe. it's the little envelope your admin command's answer comes back in 🫶

---

✨ SYNOPSIS ✨

struct nvme_mi_admin_resp_hdr {
    struct nvme_mi_msg_hdr hdr;
    __u8 status;
    __u8 rsvd0[3];
    __le32 cdw0, cdw1, cdw3;
 };

look at her. four-ish fields, absolutely no notes, serving structure realness. 💅

---

✨ Members ✨

• hdr — the Generic MI message header. like, the whole message's little name tag so everyone knows what's up.
• status — the Generic response code, and bestie listen: it's non-zero on failure. zero = we ate. anything else = we did not eat. 😭
• rsvd0 — Reserved. do not perceive her. do not touch her. she is simply there, taking up space, queen behavior. 🙈
• cdw0 — Completion Queue Entry doubleword 0.
• cdw1 — Completion Queue Entry doubleword 1.
• cdw3 — Completion Queue Entry doubleword 3.

not me noticing there's no cdw2 in the list... anyway, that's literally what the page says, so that's literally what we're saying. no inventing. periodt. 💀

---

✨ Description ✨

so what is this thing? it's the generic response format 💖 it rocks the three doublewords of completion queue data, plus optional response data. so you get your doublewords, you get your optional extras, and you get a status that will loudly tell you if things went sideways. main character response header energy, fr fr. 🔥

---

and that's the whole page, babes — no cap, no skipped bits, every single member accounted for ✨

this lil cutie came from the libnvme API Manual, and yeah it's struct nvme_mi_admin_resp_hdr up in the corner and libnvme(2) down in the footer, dated July 2026. slay, go read your completion queue entries responsibly. 💖🎀🦋