libnvme(2)

πŸ’– NAME πŸ’–

enum nvme_lba_status_cmpc β€” bestie, this is the Get LBA Status Command Completion Condition. Yes, the whole thing. That's the name. It's giving "my parents named me after a function" energy and honestly? iconic.

This one lives in the libnvme(2) API manual, aka the section for the grown-and-sexy library calls. πŸŽ€


✨ SYNOPSIS ✨

enum nvme_lba_status_cmpc {
    NVME_LBA_STATUS_CMPC_NO_CMPC ,
    NVME_LBA_STATUS_CMPC_INCOMPLETE ,
    NVME_LBA_STATUS_CMPC_COMPLETE

};

Look at her. Three little constants, all lined up, ready to tell you how done your LBA Status command actually is. πŸ¦‹


🌸 Constants 🌸

okay so these are the three moods your completion condition can be in, no cap:

  • NVME_LBA_STATUS_CMPC_NO_CMPC β€” literally no indication of the completion condition at all. it's giving "we don't know her". πŸ’€
  • NVME_LBA_STATUS_CMPC_INCOMPLETE β€” the command did complete, but plot twist: there are still additional LBA Status Descriptor Entries available to transfer, OR the scan did not complete β€” this second one only if ATYPE = 10h. so like, we're done but also we're NOT done. the duality. 😭
  • NVME_LBA_STATUS_CMPC_COMPLETE β€” she ate. πŸ’… completed the specified action over the number of LBAs specified in the Range Length field, AND transferred all available LBA Status Descriptors. full send, nothing left behind, main character energy. πŸ‘‘
lowkey important: NVME_LBA_STATUS_CMPC_INCOMPLETE is the only one carrying that little ATYPE = 10h condition, so don't go applying it to anything else, bestie. iykyk.

and that's the whole page, fr fr β€” no extra flags hiding anywhere, just three constants and their whole personality. 🧚

this was enum nvme_lba_status_cmpc from the libnvme(2) API manual, dated July 2026. thanks for reading my little manpage rant, ily, go compile something cute. πŸ’œβœ¨

πŸ“¦ where this page comes from