libnvme(9)

💖 NAME

enum nvme_id_ctrl_fcatt — bestie, this is literally the field that tells you the attributes of the controller that are specific to NVMe over Fabrics. That's it, that's the whole vibe. It's an enum in the libnvme API manual (yes, libnvme(9) — we're in the big-kid section, section 9, slay 👑).

✨ SYNOPSIS

Okay so here's the shape of it, copy it exactly, no cap:

enum nvme_id_ctrl_fcatt {
    NVME_CTRL_FCATT_DYNAMIC

};

Note the blank line before the closing brace — yes it's supposed to be there, don't come for me 🙈. And there's exactly one constant in here, NVME_CTRL_FCATT_DYNAMIC, no more, no less. Iconic minimalism 💅.

🎀 Constants

• NVME_CTRL_FCATT_DYNAMIC — okay so this one bit has two whole personalities depending on whether it's cleared or set, and both of them are about controller model:
  • If cleared → the NVM subsystem uses a dynamic controller model.
  • If set → the NVM subsystem uses a static controller model.

That's the whole lore, fr fr. Cleared = dynamic, set = static. Don't mix them up or it's giving chaos 😭🔥.

💀 tiny warning bestie: read it carefully — the cleared state is the dynamic one, which is lowkey the opposite of what your brain wants to guess. Vibe check your logic before you ship.

and that's the page!! 🦋✨ huge shoutout to the October 2026 edition of the API Manual, published under the libnvme(9) banner — this little enum page is enum nvme_id_ctrl_fcatt and it ate, no notes 🫶💜.