nvme_get_fe...ce_event_cfg(2)

💖 nvme_get_features_endurance_event_cfg — bestie's guide to the endurance event config feature ✨

okay so this one lives in the libnvme API manual (section 2, the syscall/function zone 🫶) and its full name is nvme_get_features_endurance_event_cfg. Yes the header truncates it to nvme_get_fe...ce_event_cfg(2) because even manpages have a character limit, tragic honestly 💀

---

🌸 NAME 🌸

nvme_get_features_endurance_event_cfg — get endurance event config feature 🎀

lowkey the whole point: you're asking the drive for its endurance event configuration. that's it. that's the vibe. 👑

---

✨ SYNOPSIS ✨

int nvme_get_features_endurance_event_cfg (int fd , enum
       nvme_get_features_sel sel , __u16 endgid , __u32 *result );

not me typing enum nvme_get_features_sel across two lines like that, but okay, that's just how the page wraps it 💅

---

🦋 ARGUMENTS 🦋

• fd — File descriptor of nvme device. this is your ticket to the drive, bestie, no fd no party 🙈
• sel — Select which type of attribute to return, see enum nvme_get_features_sel. you're picking what kind of attribute comes back at you ✨
• endgid — Endurance Group Identifier. yes it's spelled endgid, not endgid... wait, that IS it. anyway, it's the Endurance Group Identifier 🌈
• result — The command completion result from CQE dword0. this is where the answer lands, main character output slot 💖

---

⭐ RETURN ⭐

The nvme command status if a response was received (see enum nvme_status_field) or -1 with errno set otherwise.

so like: real status = you got a reply 🎉, -1 + errno = it went sideways and the errno is holding the receipts 😭

---

fr fr, if you get -1 back, go check errno before you do anything else. the answer is in there, i promise 💜

---

that's the whole page, bestie. four arguments, one return, zero drama. 🧚

---

written with love from the libnvme API manual, dated July 2026 — signing off, mwah 💅✨