NVME_GET_LOG_FID_SUPPORTED_EFFECTS(2)

✨ NAME ✨

nvme_get_log_fid_supported_effects β€” get the Feature Identifiers Supported and Effects log, bestie πŸ’–


🌸 SYNOPSIS 🌸

int nvme_get_log_fid_supported_effects (int fd, bool rae,
                                        struct nvme_fid_supported_effects_log *log);

πŸŽ€ ARGUMENTS πŸŽ€

  • fd β€” the file descriptor of your nvme device, aka the little handle that says "yes this drive right here" 🫢
  • rae β€” Retain asynchronous events. it's a bool, so true/false energy ✨
  • log β€” a pointer to the FID Supported and Effects data structure, where all the juicy results get dropped πŸ’…

πŸ‘‘ RETURN πŸ‘‘

So like, if a response actually came back, you get the nvme command status (peep enum nvme_status_field for the deets, iykyk). But if things went sideways? You get -1, and errno is set instead 😭 fr fr that's the whole deal.


okay that's literally it, go forth and query those feature identifiers πŸ’€βœ¨

This lil page lives under the libnvme API manual, and it was last touched in July 2026 β€” iconic, no cap πŸ‘‘πŸ’–

πŸ“¦ where this page comes from