nvme_flush(2)

💾 nvme_flush — bestie edition

okay so this is nvme_flush(2), and it lives in the libnvme API manual. it's a whole little guy whose entire job is "Send an nvme flush command" 💅 and honestly? iconic of it.

---

✨ NAME ✨

nvme_flush — sends an nvme flush command. that's it. that's the whole personality. no cap. 🎀

---

🌸 SYNOPSIS 🌸

int nvme_flush (int fd , __u32 nsid );

yep that's the whole signature, she's compact, she's efficient, she's serving 🦋

---

🫶 ARGUMENTS 🫶

• fd — the file descriptor of your nvme device. like, the actual handle to the thing. you gotta have this, bestie, there's no flushing without it 💖
• nsid — the namespace identifier. it's a __u32, it tells the command which namespace we're talking to 🌈

---

💅 DESCRIPTION 💅

so here's the vibe: the Flush command requests that the contents of volatile write cache be made non-volatile. 💫

and like… what does that MEAN. okay so imagine your device has a lil scratchpad of write cache that is, unfortunately, volatile — as in, if the power goes poof, that data goes poof too 😭. this command is you walking up and being like "hey bestie, please make that stuff non-volatile, i need it to actually survive." it's giving commit energy. it's the syncing moment. periodt 🧚

---

👑 RETURN 👑

so what do you get back:

• the nvme command status, if a response was received (peep enum nvme_status_field for the deets 🔍)
• or -1 with errno set otherwise. so like, if things went sideways, check your errno, that's your clue 💀

---

lowkey important: those two outcomes are the whole story. status if you got a response, -1 + errno if you didn't. no extra lore, that's canon 🎀

---

written by the libnvme girlies, dropped in July 2026, filed under nvme_flush in section nvme_flush(2) — mwah, go flush something, stay non-volatile 💖✨👑