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 abool, 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
- ubuntu stonking: libnvme-dev 1.16.2-1build1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms