ENUM ZFCP_DBF_SAN_ID(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum zfcp_dbf_san_id(9) β€” like, the SAN trace record identifier, bestie

okay so this is a page straight out of the Kernel API Manual, and it's honestly such a tiny iconic little enum. no cap, it's short β€” but every single value matters, so let's not skip a crumb πŸ“


✨ NAME ✨

enum zfcp_dbf_san_id β€” the SAN trace record identifier, literally. that's the whole vibe πŸ’«


πŸ¦‹ SYNOPSIS πŸ¦‹

enum zfcp_dbf_san_id {
    ZFCP_DBF_SAN_REQ ,
    ZFCP_DBF_SAN_RES ,
    ZFCP_DBF_SAN_ELS

};

like yes, that's the entire definition. three constants, no notes, she ate πŸ‘‘


πŸŽ€ Constants πŸŽ€

  • ZFCP_DBF_SAN_REQ β€” the request trace record id. that's her, the request one πŸ’–
  • ZFCP_DBF_SAN_RES β€” the response trace record id. the reply girlies 🌸
  • ZFCP_DBF_SAN_ELS β€” the extended link service record id. extended! link! service! iconic behavior ✨
heads up bestie: these are identifiers for trace records, that's it. don't go reading extra behaviour into them, the manpage doesn't and neither should you 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

the Kernel file ./drivers/s390/scsi/zfcp_dbf.h struct, plus this whole friend group right here πŸ’œ

like, that's the whole squad. read them, love them, cross-reference them 🌈


and that's the page!! mwah πŸ’‹ sign-off time: this lil beauty lives over in ./drivers/s390/scsi, dated October 2026, and it's still called enum zfcp_dbf_san_id(9) β€” fr fr, slay πŸŒŸπŸŽ€

πŸ“¦ where this page comes from