libnvme(9)

📦 version 3.2, in arch rolling

💅 libnvme(9) — the API manual, bestie edition

Okay so this page is from the API Manual (that's the manual name, slay) and it's literally all about one little enum. One. Iconic, honestly.

✨ NAME ✨

enum nvme_resv_cptpl — Reservation Register - Change Persist Through Power Loss State 🎀

Like, yes, that's a whole mouthful. It's the enum that controls what happens to your reservations when the power goes bye 💀.

🌸 SYNOPSIS 🌸

enum nvme_resv_cptpl {
    NVME_RESERVATION_CPTPL_NO_CHANGE ,
    NVME_RESERVATION_CPTPL_CLEAR ,
    NVME_RESERVATION_CPTPL_PERSIST

};

Three constants, no notes, we love a short synopsis 🫶 (and yes, the trailing comma-free blank line before the closing brace is exactly how it's written, don't come for me).

👑 Constants 👑

So here's the vibe check on each one, fr fr:

  • NVME_RESERVATION_CPTPL_NO_CHANGE — literally no change to the PTPL state. Nothing happens. Zero drama. The "leave me alone, I'm fine" option 🙈
  • NVME_RESERVATION_CPTPL_CLEAR — on a power on, reservations are released and registrants are cleared. So yeah, the power blips and everything gets wiped. It's giving "start of a new semester, fresh notebook" energy 😭
  • NVME_RESERVATION_CPTPL_PERSIST — reservations and registrants persist across a power loss. Unbothered. Unmoved. Main character energy that survives the blackout 🔥👑
ngl, three options, that's the whole page. Short king of a manpage.

That's it, that's the page, bestie 💖 — this was enum nvme_resv_cptpl from the libnvme(9) API manual, dated October 2026. Go forth and persist (or don't, your call, NO_CHANGE is valid too) 🦋

📦 where this page comes from