libnvme(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… libnvme(9) β€” the API Manual, bestie edition πŸŽ€

okay so this is a page from the libnvme API manual (yes, libnvme(9), she's famous ✨) and it's honestly a tiny one, so let's just get into it 🫢


🌸 NAME 🌸

enum nvme_id_ctrl_vwc β€” literally the Volatile write cache enum. that's her whole job. iconic for that ngl πŸ’œ


✨ SYNOPSIS ✨

here's exactly what she looks like, no cap, copy it character for character:

enum nvme_id_ctrl_vwc {
    NVME_CTRL_VWC_PRESENT ,
    NVME_CTRL_VWC_FLUSH

};

two constants, one enum, zero drama πŸ¦‹ (except the drama that the write cache itself brings, we'll get there).


πŸ‘‘ Constants πŸ‘‘

πŸ’– NVME_CTRL_VWC_PRESENT

if this bit is set, it indicates a volatile write cache is present. so like… she exists, she's real, she's in the building πŸ’…

and if a volatile write cache is present, then the host controls whether the volatile write cache is enabled with a Set Features command specifying the value NVME_FEAT_FID_VOLATILE_WC. so the host is the main character here and the cache is taking direction from her, periodt πŸ‘‘

🫢 tiny vibe check: the host is the one flipping that switch β€” it's the Set Features command with NVME_FEAT_FID_VOLATILE_WC that does it. remember the exact name, iykyk.

πŸŽ€ NVME_CTRL_VWC_FLUSH

this one is a mask to get the value of the flush command behavior. that's it. she's a mask, she reveals the flush behavior, she ate and left no crumbs πŸ“


that's the whole page bestie, she's short but she said what she said πŸ’€βœ¨

mwah πŸ’‹ this little moment was brought to you by the October 2026 edition of the libnvme(9) manual β€” go drink some water, then go flush that cache responsibly πŸŒˆπŸ’œ

πŸ“¦ where this page comes from