libnvme(2)

💖 NAME 💖

ok so this is all about enum nvme_psd_flags — literally just the possible flag values that can show up in an nvme power state descriptor. that's it. that's the whole vibe. and yes bestie this is from the libnvme API manual, the libnvme(2) page, so you're in the right place 🫶

---

✨ SYNOPSIS ✨

here's the enum in all its glory, characters preserved, no notes:

enum nvme_psd_flags {
    NVME_PSD_FLAGS_MXPS ,
    NVME_PSD_FLAGS_NOPS

};

---

🎀 Constants 🎀

okay these are the two constants, and they're both just single bits doing very specific little jobs. let's get into it 💅

• NVME_PSD_FLAGS_MXPS — bestie this one is the scale for the Maximum Power field, and the way it works is very much a vibe check on units:
  • if this bit is cleared, then the scale of the Maximum Power field is in 0.01 Watts.
  • if this bit is set, then the scale of the Maximum Power field is in 0.0001 Watts.

so yeah, one little bit and suddenly your watts have four decimal places instead of two. iconic honestly 😭✨

• NVME_PSD_FLAGS_NOPS — this one is the does-this-controller-actually-do-work-here bit. it tells you whether the controller processes I/O commands in this power state:
  • if this bit is cleared, then the controller does process I/O commands in this power state.
  • if this bit is set, then the controller does not process I/O commands in this power state.

so like, set means it's napping. clearing means it's awake and serving. nap time vs main character energy, basically 👑

ngl the naming here is doing the most — "NOPS" is giving "no operations" and yeah, that's exactly what a set bit means. lowkey elegant. 🦋

---

and that's the whole page, bestie, we ate and left no crumbs 🍓💜

this was the enum nvme_psd_flags page from the libnvme API manual, dated July 2026 — mwah, go forth and read your power state descriptors 🌸🎀💖