libnvme(9)

✨ NAME ✨

enum nvme_nvmset_pl_events — bestie, this is the Predictable Latency Per NVM Set Log — Event Type enum, and yes that's a mouthful, but it's literally just the list of event types that show up in that log 🎀

🌸 SYNOPSIS 🌸

enum nvme_nvmset_pl_events {
    NVME_NVMSET_PL_EVENT_DTWIN_READ_WARN ,
    NVME_NVMSET_PL_EVENT_DTWIN_WRITE_WARN ,
    NVME_NVMSET_PL_EVENT_DTWIN_TIME_WARN ,
    NVME_NVMSET_PL_EVENT_DTWIN_EXCEEDED ,
    NVME_NVMSET_PL_EVENT_DTWIN_EXCURSION

};

That trailing comma situation before the closing brace? Yeah, it's just Like That in the source, don't come for me 💅

⭐ Constants ⭐

Okay so here's the whole cast of characters, one by one 👑

• NVME_NVMSET_PL_EVENT_DTWIN_READ_WARN — the DTWIN Reads Warning, aka the lil heads-up that your reads are drifting out of the deterministic window 🙈
• NVME_NVMSET_PL_EVENT_DTWIN_WRITE_WARN — the DTWIN Writes Warning — same vibe check, but for writes ✍️
• NVME_NVMSET_PL_EVENT_DTWIN_TIME_WARN — the DTWIN Time Warning, the clock-based one tickin' at you ⏰
• NVME_NVMSET_PL_EVENT_DTWIN_EXCEEDED — the Autonomous transition from DTWIN to NDWIN due to typical or maximum value exceeded 😭 like the drive just... decides on its own, no permission asked, because something hit typical or maximum. Iconic but rude.
• NVME_NVMSET_PL_EVENT_DTWIN_EXCURSION — the Autonomous transition from DTWIN to NDWIN due to Deterministic Excursion 💀 again fully autonomous, but this time the reason is a Deterministic Excursion. Different reason, same dramatic exit.

ngl, those last two both mean "DTWIN to NDWIN, and nobody asked you first." Read the reason field, bestie, that's the whole plot 🫶

and that's the whole page, no cap 🦋

This lil beauty is from the libnvme API Manual, libnvme(9), page dated October 2026 — so go forth, log your events, and slay ✨💖