libnvme(2)

πŸ’– NAME πŸ’–

okay bestie, listen up β€” this is libnvme, the API manual, and we're about to meet the absolute icon that is struct nvme_format_nvm_compln_event πŸŽ€βœ¨

it's literally the Format NVM Completion Event Data struct. that's its whole job. it holds the data that shows up when a Format NVM command finishes doing its thing. no cap. πŸ’…


✨ SYNOPSIS ✨

the way she's built, fr fr:

struct nvme_format_nvm_compln_event {
    __le32 nsid;
    __u8 smallest_fpi;
    __u8 format_nvm_status;
    __le16 compln_info;
    __le32 status_field;
 };

like… look at that layout. every field placed with intention. main character energy only. πŸ‘‘


πŸ¦‹ Members πŸ¦‹

  • nsid β€” the Namespace Identifier. it's a __le32. she tells you which namespace this whole event is about. your fave, basically. 🌸
  • smallest_fpi β€” the Smallest Format Progress Indicator. it's a __u8. yes it's tiny. no we don't disrespect it. progress is progress. 🫢
  • format_nvm_status β€” the Format NVM Status. it's a __u8. this is the vibe check on how the format went. πŸ‘€
  • compln_info β€” the Completion Information. it's a __le16. the little extra tea that comes along with the completion. β˜•πŸ’œ
  • status_field β€” the Status Field. it's a __le32. the big status moment. it ate and left no crumbs. πŸ”₯

πŸ’– quick reminder bestie: every one of these fields is stored exactly as declared up there. __le32, __u8, __u8, __le16, __le32 β€” in that order, no reordering, no "improving" it. the struct said what it said. periodt. πŸ’…

that's the whole page, and honestly? iconic. slayed. 🌈⭐

this was libnvme(2) β€” the API manual β€” dishing out struct nvme_format_nvm_compln_event for you, dated July 2026. mwah, go format something (responsibly). πŸŽ€πŸ’–πŸ§š

πŸ“¦ where this page comes from