libnvme(2)

💖 libnvme(2) — the API manual, bestie edition 💖

okay so welcome to the libnvme manual page, section 2 (that's the API one, iykyk). today's main character is a lil enum that tells you which way the data is going. that's literally it. that's the whole vibe. and yet. it's iconic. 🦋

---

✨ NAME ✨

enum nvme_data_tfr — the enum that says which direction data is flowing in a command, bestie. no cap.

---

🌸 SYNOPSIS 🌸

enum nvme_data_tfr {
    NVME_DATA_TFR_NO_DATA_TFR ,
    NVME_DATA_TFR_HOST_TO_CTRL ,
    NVME_DATA_TFR_CTRL_TO_HOST ,
    NVME_DATA_TFR_BIDIRECTIONAL

};

like. look at her. four constants. perfect. no notes. 💅

---

🎀 Constants 🎀

okay so here's the whole squad, one by one:

• NVME_DATA_TFR_NO_DATA_TFR — no data transfer. like, none. zero. the command is just vibing, not moving any bytes anywhere. 🫶
• NVME_DATA_TFR_HOST_TO_CTRL — host to controller. data goes from the host over to the controller. she's leaving home. ✨
• NVME_DATA_TFR_CTRL_TO_HOST — controller to host</c> — ugh wait, sorry, let me redo that: controller to host. data comes back from the controller to the host. she's coming home. 😭
• NVME_DATA_TFR_BIDIRECTIONAL — bidirectional. going both ways. main character energy fr fr, she does it all. 🔥

---

reminder bestie: no data transfer, host to controller, controller to host, and bidirectional are the exact meanings of these constants. i am not embellishing. i am simply relaying the facts with ✨flair✨.

---

and that's the page!! 🎀 thanks for reading, love u, mwah 💖

okay so the boring-but-required bit: this was the enum nvme_data_tfr page out of libnvme(2), dated July 2026, and it's part of the big libnvme API manual. periodt. 👑