sas_get_port_device(9)
β¨ sas_get_port_device(9) β¨
okay bestie, this is the Kernel API Manual entry for sas_get_port_device(9), and we are about to make device discovery make sense. no cap. π«Ά
πΈ NAME πΈ
sas_get_port_device β discover devices which caused port creation π
π¦ SYNOPSIS π¦
int sas_get_port_device (struct asd_sas_port *port );
π ARGUMENTS π
portβ pointer tostruct sas_portof interest. (and yes, the synopsis saysstruct asd_sas_port *portβ both of those exact names are in the original, so don't come for me π )
π₯ DESCRIPTION π₯
okay so here's the actual tea, and it's iconic:
- Devices directly attached to a HA port have no parent. This is how we know they are (domain)
"root"devices. π± - All other devices do, and should have their
"parent"pointer set appropriately as soon as a child device is discovered. π
π SEE ALSO π
go give these a read, bestie β they're all part of the same main-character discovery arc:
- Kernel file
./drivers/scsi/libsas/sas_discover.c sas_discover_end_dev(9)sas_discover_domain(9)sas_init_disc(9)
okay bye bestie! π«Ά this page comes from the ./drivers/scsi/libsas source/version and is dated October 2026 β mwah, stay slaying π
β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms