libnvme(9)

✨ NAME ✨

enum nvme_feat_perfc_attri — the performance characteristics attribute index 🎀

okay so this is a little enum from the libnvme API Manual, and its whole ~thing~ is indexing performance characteristics attributes. that's it, that's the vibe 💅

🌸 SYNOPSIS 🌸

bestie, here's the whole shape of it, character for character 👑

enum nvme_feat_perfc_attri {
    NVME_FEAT_PERFC_ATTRI_STD ,
    NVME_FEAT_PERFC_ATTRI_ID_LIST ,
    NVME_FEAT_PERFC_ATTRI_VS_MIN ,
    NVME_FEAT_PERFC_ATTRI_VS_MAX

};

lowkey iconic that NVME_FEAT_PERFC_ATTRI_VS_MAX gets a whole blank line to itself before the closing brace. main character energy fr fr 🦋

💅 Constants 💅

four constants, no cap, and every single one matters:

• NVME_FEAT_PERFC_ATTRI_STD — the standard performance attribute ⭐ like the default/default default of this whole situation
• NVME_FEAT_PERFC_ATTRI_ID_LIST — the performance attribute identifier list 🍓 a whole list of identifiers, slay
• NVME_FEAT_PERFC_ATTRI_VS_MIN — the vendor specific performance attribute minimum index 🌸 the floor, the starting point, the "we begin here" of the vendor-specific zone
• NVME_FEAT_PERFC_ATTRI_VS_MAX — the vendor specific performance attribute maximum index 🔥 the ceiling, the end of the line, the final boss of vendor-specific indices

ngl there's nothing sneaky in here — it's just an index enum. but knowing the min and the max of the vendor specific range? that's the kind of detail that makes you look like you know things. because you do now 🫶

and that's the whole page!! short and sweet and honestly kind of a vibe check passed with flying colors 🌈 this was the libnvme(9) page from the API Manual, dated October 2026, and yes the footer really did say enum nvme_feat_perfc_attri and libnvme(9) again, so consider it shouted out properly 💖✨🎀