libnvme(2)

💖 libnvme — enum nvme_id_ctrl_vwci 💖

okay bestie, welcome to the libnvme manual (section 2, the API one, iykyk ✨). today we're doing one (1) enum and honestly? it's giving niche-but-important. let's go 🫶

---

✨ NAME ✨

enum nvme_id_ctrl_vwci — this field tells you the tea about how many times you can still update your VPD contents using the VPD Write command. and if you wanna see the bigger picture, go peek at &struct nvme_id_ctrl.vwci 💅

---

🌸 SYNOPSIS 🌸

enum nvme_id_ctrl_vwci {
    NVME_CTRL_VWCI_VWCR ,
    NVME_CTRL_VWCI_VWCRV

};

---

🎀 Constants 🎀

no cap, there are exactly two of them and both are literally about the same counter. here they are, in order, no skips:

• NVME_CTRL_VWCI_VWCR — this is the mask you use to get the value of VPD Write Cycles Remaining 🍓. so: if the VPD Write Cycle Remaining Valid bit is set, then this field holds a value telling you how many times you've still got left to update VPD contents with the VPD Write command. and if this field is set to 7Fh, then the remaining number of times you can update VPD contents using the VPD Write command is greater than or equal to 7Fh — so like, a lot, it's not giving exact numbers anymore 💀.
• NVME_CTRL_VWCI_VWCRV — VPD Write Cycle Remaining Valid, the vibe check bit ✨. if this bit is set, then the VPD Write Cycle Remaining field is valid, slay, trust it 👑. if this bit is cleared, then the VPD Write Cycles Remaining field is invalid and cleared to 0h — so don't you dare read meaning into it 🙈.

---

fr fr reminder: those two fields are a package deal. the mask only means something when the valid bit says it does. read the bit first, bestie 🦋

---

💜 that's the whole page, no fillers, no fluff, just a tiny enum with main character energy.

sign-off time 🎀 this page is enum nvme_id_ctrl_vwci from the libnvme manual, section 2, dated July 2026. periodt. go write some VPD 💅✨