libnvme(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… NAME

enum nbft_ssns_ext_info_flags β€” the Subsystem and Namespace Extended Information Descriptor Flags, bestie ✨

Like, this is the little flags enum from the libnvme(9) API manual, and she's here to tell you which bits in the SSNS extended info descriptor are doing something and which are just, uh, reserved vibes 🫢


πŸ¦‹ SYNOPSIS

enum nbft_ssns_ext_info_flags {
    NBFT_SSNS_EXT_INFO_VALID ,
    NBFT_SSNS_EXT_INFO_ADMIN_ASQSZ

};

No cap, that's the whole thing β€” two constants, and every single one of them matters πŸ’–


🌸 Constants

  • NBFT_SSNS_EXT_INFO_VALID β€” Descriptor Valid πŸŽ€ If it's set to 1h, then this descriptor is valid, periodt. If it's cleared to 0h, then this descriptor is reserved β€” so like, don't come for her, she's just not in use πŸ™ˆ
  • NBFT_SSNS_EXT_INFO_ADMIN_ASQSZ β€” Administrative ASQSZ πŸ‘‘ If it's set to 1h, then the value of the ASQSZ field was provided by administrative configuration for this SSNS record β€” someone literally hand-picked it, main character energy ✨ If it's cleared to 0h, then the value of the ASQSZ field was either obtained by discovery or assumed by the driver, iykyk πŸ¦‹
Heads up bestie: 1h and 0h are the two states here, and the 0h case on NBFT_SSNS_EXT_INFO_VALID means the descriptor is reserved β€” not "invalid data", just reserved πŸ’€

okay that's the whole page, mwah πŸ’… that was enum nbft_ssns_ext_info_flags from the API Manual of libnvme(9), and the date on this one is October 2026 β€” slay, see you in the group chat πŸ§šβ€β™€οΈπŸ’œ

πŸ“¦ where this page comes from