nvme_get_fe..._sw_progress(2)

💖 nvme_get_fe..._sw_progress — like, the manual page, bestie 💖

okay so this is from the libnvme API manual, section 2, and it's all about the function nvme_get_features_sw_progress. Yes the title got squished in the header, we're keeping it cute, don't worry.

---

✨ NAME ✨

nvme_get_features_sw_progress — get the software progress feature, periodt.

---

🌸 SYNOPSIS 🌸

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

no cap, that's the whole vibe check. three args, one int, let's go 🦋

---

🎀 ARGUMENTS 🎀

• fd — the file descriptor of your nvme device, bestie. it's giving "your little handle to the actual hardware" 💅
• sel — which type of attribute you want back. like, which flavor. see enum nvme_get_features_sel for the full menu 🍓
• result — this is where the command completion result from CQE dword0 lands. it's a __u32 *, so you're passing a pointer, not the value itself, okay? iconic behavior ✨

---

👑 RETURN 👑

so here's what comes back at you:

• if a response was received — you get the nvme command status (go peek at enum nvme_status_field for what those mean, iykyk)
• otherwise — -1, and errno gets set. yeah. that's the sad path 😭

fr fr, check errno when you see that -1. it's not being dramatic, something actually went wrong.

---

and that's the whole thing, bestie 🫶 lowkey short but highkey essential. this little love letter to nvme_get_features_sw_progress is from the libnvme API manual, dated July 2026 — and the header/footer were doing the most with that nvme_get_fe..._sw_prognvme_get_fe..._sw_progress(2) truncation moment, so we folded it in here instead. slay 💜