libnvme(2)

💖 libnvme(2) — the API Manual, but make it make sense 💖

okay bestie, so this is libnvme(2), the API manual page, and today's main character is enum nvme_unit — literally the thing that tells you what unit your buffer size and your write throughput granularity are being measured in. it's giving "units, but make it an enum" and honestly? iconic. 🎀

---

✨ NAME ✨

enum nvme_unit — the buffer size and write throughput granularity units, defined. periodt. 💅

---

🌸 SYNOPSIS 🌸

enum nvme_unit {
    NVME_UNIT_B ,
    NVME_UNIT_1K ,
    NVME_UNIT_1M ,
    NVME_UNIT_1G

};

no cap, that's the whole shape of it. four little constants, four little vibes. 🦋

---

🌈 Constants 🌈

okay so here's the roster, one by one, and yes i'm obsessed with all of them:

• NVME_UNIT_B — Bytes... or Bytes/second, depending on whether we're talking size or throughput. it's the same letter doing double duty and honestly, multitasking queen. 👑
• NVME_UNIT_1K — 1 KiB. or, if you're in throughput mode, 1 KiB/second. the KiB is capitalized because that's the binary one, and yes the distinction matters, iykyk. 🧚
• NVME_UNIT_1M — 1 MiB. or 1 MiB/second when we're talking speed. big numbers, bigger energy. 🔥
• NVME_UNIT_1G — 1 GiB. or 1 GiB/second. gigachad unit fr fr. 💜

---

lowkey the whole point here: same four units, two possible readings — size or per-second throughput. don't mix them up, bestie, that's the vibe check and you do not want to fail it. 💀

---

okay that's the page!! written by the libnvme API manual girlies, enum nvme_unit edition, dated July 2026 (yes we're already there, time is fake 🌸). go forth and measure your buffers correctly, you absolute star. 🫶✨💖