libnvme(2)

💖 libnvme(2) — API Manual 💖

okay bestie, welcome to the libnvme API manual ✨ this is a page from the API Manual, section 2, and today's main character is a lil struct called nvme_mi_msg_hdr. yes babes we're doing structured wire formats, it's giving very cutesy very demure, let's go 🎀

---

✨ NAME ✨

struct nvme_mi_msg_hdr — the General MI message header, aka the little header that starts every MI message like a name tag at a party 🫶

---

🌸 SYNOPSIS 🌸

struct nvme_mi_msg_hdr {
    __u8 type;
    __u8 nmp;
    __u8 meb;
    __u8 rsvd0;
 };

four whole bytes bestie, four. tiny king energy 👑

---

🦋 Members 🦋

• type — the MCTP message type, and it will always be NVME_MI_MSGTYPE_NVME. like no matter what, it's that one. periodt 💅
• nmp — NVMe-MI message parameters (this is the one that includes the MI message type, iykyk) 🌈
• meb — the Management Endpoint Buffer flag; it's unused for the libnvme-mi implementation. so like, it's there, it's cute, it's just not doing anything 🙈
• rsvd0 — currently reserved. hands off babe, it's saving that spot 🔒

---

💜 Description 💜

So this is the wire format that gets shared by both request messages AND response messages, per NVMe-MI section 3.1 ✨ and it's used for literally all message types — MI and Admin. every single one. it's the communal glue of the whole thing fr fr 🧚

---

ngl this is one of the chillest structs in the whole API, no cap. memorize those four bytes and you're slaying 💖

and that's the vibe check for today bestie! this page is from libnvme(2) — the API Manual, dated July 2026 — and it covers struct nvme_mi_msg_hdr. ty for reading, mwah, go write some iconic code 🌸✨💅