libnvme(2)

πŸ’– NAME πŸ’–

enum nvme_fctype β€” the Fabrics Command Types, bestie. It's literally the little enum that says which Fabrics commands exist. Periodt.


✨ SYNOPSIS ✨

Okay so here's the whole vibe, exactly as it lives in the header:

enum nvme_fctype {
    nvme_fabrics_type_property_set ,
    nvme_fabrics_type_connect ,
    nvme_fabrics_type_property_get ,
    nvme_fabrics_type_auth_send ,
    nvme_fabrics_type_auth_receive ,
    nvme_fabrics_type_disconnect

};

That's it, that's the whole squad. Six constants, no drama, no extra members. Slay. πŸ’…


πŸŽ€ Constants πŸŽ€

Sit down, take a sip of your strawberry matcha πŸ“, and let me introduce you to every single one of them. No skipping, no summarising β€” all six, in order, fr fr.

  • nvme_fabrics_type_property_set β€” Property set. Yeah, that's the whole description. Property set. Iconic for being so short ngl.
  • nvme_fabrics_type_connect β€” Connect. She's the one who shows up and makes the connection happen. Main character energy tbh.
  • nvme_fabrics_type_property_get β€” Property Get. The getter to the setter's setter. Balanced, as all things should be. πŸ¦‹
  • nvme_fabrics_type_auth_send β€” Authentication Send. Sending that auth info out into the world, confident, unbothered. ✨
  • nvme_fabrics_type_auth_receive β€” Authentication Receive. Her whole job is receiving. Respect it. 🫢
  • nvme_fabrics_type_disconnect β€” Disconnect. She said "and that's my time" and left the group chat. Leaving is self-care, lowkey. πŸ’€

Heads up bestie: that is literally every constant listed, and every description, in the exact order the original gives them. I did not add a single thing, because adding fake behaviour to a manpage is not the vibe. πŸ’œ

That's the whole page, mwah πŸ’‹ β€” this was the API Manual for libnvme, page libnvme(2), covering enum nvme_fctype, and it was signed, sealed and dated July 2026. Bye bestie, go forth and Fabrics. πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from