libnvme(2)

💖 NAME 💖

enum nvme_id_ns_mc — bestie, this is the enum that spills the tea on what a namespace can actually do with metadata 👑

---

✨ SYNOPSIS ✨

enum nvme_id_ns_mc {
    NVME_NS_MC_EXTENDED ,
    NVME_NS_MC_SEPARATE

};

---

🎀 Constants 🎀

okay so there are exactly two constants in this enum and they are both little flags telling you how the namespace likes its metadata served. let's get into it 🦋

• NVME_NS_MC_EXTENDED — if this bit is set, it means the namespace is out here supporting metadata being transferred as part of a separate buffer that gets specified in the Metadata Pointer. no cap, that's the whole vibe. 💅
• NVME_NS_MC_SEPARATE — if this bit is set, it means the namespace supports the metadata being transferred as part of an extended data LBA. periodt. 🌸

---

ngl bestie, both of these are just "if set" situations — so a clear bit means that flavor of metadata transfer is simply not the move for that namespace. check your bits, always. 💀

---

and that's the whole page, you ate that 🫶 this gem lives in the API Manual for libnvme — it's manual page libnvme(2), the enum nvme_id_ns_mc entry, dated July 2026. mwah, go read some more manpages 💜