libnvme(2)

πŸ’– NAME πŸ’–

okay so bestie, this is the manual page for enum nvme_mi_dtyp β€” the Data Structure Type field, and yes it literally ate πŸ’…

It's part of the libnvme API manual, section 2, iykyk ✨


✨ SYNOPSIS ✨

enum nvme_mi_dtyp {
    nvme_mi_dtyp_subsys_info ,
    nvme_mi_dtyp_port_info ,
    nvme_mi_dtyp_ctrl_list ,
    nvme_mi_dtyp_ctrl_info ,
    nvme_mi_dtyp_opt_cmd_support ,
    nvme_mi_dtyp_meb_support

};

like… a whole little enum just vibing 🌸 six constants, no more no less, periodt.


πŸŽ€ Constants πŸŽ€

okay so these are the little squad members, and every single one matters, no cap 🫢

  • nvme_mi_dtyp_subsys_info β€” NVM Subsystem Information 🌈 the tea about your subsystem
  • nvme_mi_dtyp_port_info β€” Port information πŸ¦‹ all the port deets
  • nvme_mi_dtyp_ctrl_list β€” Controller List πŸ‘‘ who's who in controller land
  • nvme_mi_dtyp_ctrl_info β€” Controller Information πŸ’œ the controller's whole personality
  • nvme_mi_dtyp_opt_cmd_support β€” Optionally Supported Command List ⭐ the "we might support this" list, iconic
  • nvme_mi_dtyp_meb_support β€” Management Endpoint Buffer Command Support List πŸ’€ the MEB support receipts

πŸ’… Description πŸ’…

So fr fr, this is the Data Structure Type field for the Read NVMe-MI Data Structure command πŸ”₯

not me explaining it β€” basically it's the thingy that tells the endpoint which particular structure you want to query from it 🧚

so you pick a value, you slide it into that field, and the endpoint knows exactly which structure to hand back. slay. no guessing, no chaos, just a clean little "hey bestie, gimme this one" 🌸

⚠️ heads up: the field only indicates the structure to query β€” that's its whole job, don't make it carry more than that πŸ’–

that's the whole page, babe 🫢 no notes, it's giving minimalist icon ⭐

libnvme Β· enum nvme_mi_dtyp Β· July 2026 πŸŽ€ bye bestie, go query something πŸ’œ

πŸ“¦ where this page comes from