nvme_set_features_data(2)

💖 nvme_set_features_data — bestie edition ✨

okay so real talk, this is a page from the libnvme API manual, and you're about to meet nvme_set_features_data 🎀

---

🌸 NAME 🌸

nvme_set_features_data — the little helper function that does the heavy lifting for its bestie nvme_set_features() 🫶

---

✨ SYNOPSIS ✨

int nvme_set_features_data (int fd , __u8 fid , __u32 nsid , __u32 cdw11
, bool save , __u32 data_len , void *data , __u32 *result );

yes, that's the whole signature, copied character for character because we do NOT play with code accuracy 💅

---

🌈 ARGUMENTS 🌈

• fd — the file descriptor of your nvme device, aka your ticket in 🎟️
• fid — the feature identifier, like a little name tag for which feature we're talking about 👑
• nsid — the namespace ID, but only if applicable — sometimes it's just not that girl 🙈
• cdw11 — the value you're setting the feature to, the whole point of the operation fr fr 💖
• save — whether to save that value across power states, so it survives the nap 😴🔋
• data_len — the length of the feature data, in bytes, if applicable 📏
• data — the user address of the feature data, again if applicable 🏠
• result — the command completion result, straight from CQE dword0, no filter, no cap 💯

---

💫 RETURN 💫

So here's what 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, if things did not go how we wanted 😭

no cap, -1 means it's giving error vibes. check that errno, bestie, it's trying to tell you something 🚨

---

and that's the whole page, periodt 💅 thank u for coming to my ted talk, this manual comes to you from the libnvme API manual, dated July 2026 — the same date that lives down in the footer where the source and version hang out 🦋 mwah, go set some features 🌸✨