libnvme(2)

🌸 NAME 🌸

enum nvme_id_ns_dlfeat — bestie, this enum is the whole vibe check for a namespace: it tells you all about the features that affect deallocating logical blocks for this namespace. 💖

---

✨ SYNOPSIS ✨

enum nvme_id_ns_dlfeat {
    NVME_NS_DLFEAT_RB ,
    NVME_NS_DLFEAT_RB_NR ,
    NVME_NS_DLFEAT_RB_ALL_0S ,
    NVME_NS_DLFEAT_RB_ALL_FS ,
    NVME_NS_DLFEAT_WRITE_ZEROES ,
    NVME_NS_DLFEAT_CRC_GUARD

};

---

🎀 Constants 🎀

okay so these are the members, and every single one of them is iconic in its own little way 🫶

• NVME_NS_DLFEAT_RB — it's giving mask. This one masks out the bits so you can actually read the value of the read behavior. 🌈
• NVME_NS_DLFEAT_RB_NR — lowkey rude but okay: the read behavior is literally not reported. 🙈
• NVME_NS_DLFEAT_RB_ALL_0S — when a logical block gets deallocated, it comes back with all bytes cleared to 0h. squeaky clean. ✨
• NVME_NS_DLFEAT_RB_ALL_FS — same deallocated logical block energy, except all the bytes come back set to FFh. iconic contrast. 💜
• NVME_NS_DLFEAT_WRITE_ZEROES — if this bit is set, it means the controller supports the Deallocate bit in the Write Zeroes command for this namespace. no cap, that's the whole thing. 🔥
• NVME_NS_DLFEAT_CRC_GUARD — if this bit is set, the Guard field for deallocated logical blocks that carry protection information is set to the CRC for the value read from the deallocated logical block and its metadata. yeah it's a mouthful, but it ate. 💅

---

fr fr bestie, that's the entire page — nothing skipped, nothing extra, just the facts with a lil sparkle. 🦋

and that's a wrap on the enum nvme_id_ns_dlfeat page from the libnvme(2) API manual, dated July 2026 — ty for coming to my TED talk, mwah 💖🎀✨