NVME_GET_FEATURES_WRITE_ATOMIC(2)

✨ nvme_get_features_write_atomic(2) ✨

okay bestie, welcome to the libnvme API manual, section 2 💖 this one's called nvme_get_features_write_atomic — and yeah, the header squishes the name down to nvme_get_fea...write_atomic(2) bc terminals are dramatic like that, but we know her full name and we're obsessed 🫶

---

🌸 NAME 🌸

nvme_get_features_write_atomic — get the write atomic feature, that's it, that's the whole vibe ✨

---

🎀 SYNOPSIS 🎀

int nvme_get_features_write_atomic (int fd , enum nvme_get_features_sel
sel , __u32 *result );

(it's giving "three args and a dream" 💅)

---

🦋 ARGUMENTS 🦋

• fd — the file descriptor of your nvme device. yes, the whole device. main character energy, no cap 👑
• sel — picks which type of attribute you want back. it's an enum nvme_get_features_sel, so go look at that enum, iykyk 🌈
• result — a __u32 * that catches the command completion result from CQE dword0. literally where the answer lands, periodt 💀

---

⭐ RETURN ⭐

if a response came back, you get the nvme command status (check enum nvme_status_field for the tea 🍓). otherwise it's -1 with errno set, so check that errno bestie, don't just stand there 🙈

---

ngl, nothing here is dangerous — it's a getter — but please. check the return value. your future self will thank you 💜

---

and that's the page!! 🌟 this came from the libnvme API manual, dated July 2026 (the footer kept whispering nvme_get_fea...write_atomic(2) at us the whole time, iconic honestly). go forth and fetch that feature, you're doing amazing sweetie 🧚✨🎀