libnvme(9)

💖 libnvme — struct nvme_mi_aem_occ_data 💖

okay bestie, so this is a page straight out of the libnvme API Manual, and we're talking about one little struct that does a big job. sit down, grab a strawberry 🍓, and let's get into it.

---

🌸 NAME 🌸

struct nvme_mi_aem_occ_data — AEM Message definition. yes that's the whole vibe. one struct. iconic behavior.

---

✨ SYNOPSIS ✨

here's the literal shape of it, no cap:

struct nvme_mi_aem_occ_data {
    __u8 aelhlen;
    __u8 aeosil;
    __u8 aeovsil;
    struct {
      __u8 aeoi;
      __le32 aeocidi;
      __u8 aessi;
    } aeoui;
 };

look at her. nested struct and everything. main character energy fr fr 👑

---

🎀 Members 🎀

• aelhlen — the AE Occurrence Header Length. literally how long the header part is.
• aeosil — the AE Occurrence Specific Info Length. tells you how much occurrence-specific info is riding along.
• aeovsil — the AE Occurrence Vendor Specific Info Length. same energy, but for the vendor-specific info.
• aeoui — the AE Occurrence Unique ID, and the way that it's lowkey made up of other subfields?? yeah. it's a little squad of its own.

---

🦋 Description 🦋

so this struct is one single entry of AE occurrence data, and it comes attached to an nvme_aem_msg. cute, right?

and here's the part you gotta know: right after this structure comes the variable length AEOSI (occurrence specific info) and the variable length AEVSI (vendor specific info). the length of AEOSI is specified by aeosil, and the length of AEVSI is specified by AEVSI.

💀 heads up: neither field is mandatory, and they shall be omitted if their length parameter is set to zero. so if the length is zero, the field is just... not there. bye bestie 👋

---

🌈 SEE ALSO 🌈

nothing extra on this one, bestie — this page keeps it tight. (iykyk)

---

and that's the whole page!! 💅 this was libnvme(9), part of the API Manual, and the footer was stamped August 2026 ✨ go forth and parse your AEM messages, you absolute genius 🫶🎀