libnvme(2)

πŸ’– libnvme(2) β€” API Manual πŸ’–

okay so bestie, welcome to the libnvme API manual, section 2. this is literally the enum glow-up page and i'm obsessed 🫢


✨ NAME ✨

enum nvme_telemetry_da β€” Telemetry Log Data Area

like. the whole vibe of this page is "which data area are we talking about" and the answer is a lil numbered menu πŸ’…


🌸 SYNOPSIS 🌸

enum nvme_telemetry_da {
    NVME_TELEMETRY_DA_CTRL_DETERMINE ,
    NVME_TELEMETRY_DA_1 ,
    NVME_TELEMETRY_DA_2 ,
    NVME_TELEMETRY_DA_3 ,
    NVME_TELEMETRY_DA_4

};

look at her. five constants, all lined up, absolutely serving πŸŽ€


πŸ¦‹ Constants πŸ¦‹

okay so here's the rundown, one by one, no skips, no notes:

  • NVME_TELEMETRY_DA_CTRL_DETERMINE β€” the controller decides which data areas get created. it's giving "you pick, i trust you" energy ✨
  • NVME_TELEMETRY_DA_1 β€” Data Area 1 πŸ’–
  • NVME_TELEMETRY_DA_2 β€” Data Area 2 🌸
  • NVME_TELEMETRY_DA_3 β€” Data Area 3 πŸ¦‹
  • NVME_TELEMETRY_DA_4 β€” Data Area 4 πŸ’…

literally one through four, in order, exactly like that. the way the numbers just go up? iconic. periodt πŸ‘‘


fr fr bestie, that's the entire enum. no hidden flags, no surprise env vars, no sneaky exit statuses. just five constants living their best life 🌈

and that's the whole page, diva πŸ’œ β€” this was enum nvme_telemetry_da from the libnvme(2) API manual, dated July 2026. go forth and pick your data area, you got this 🫢✨

πŸ“¦ where this page comes from