mpt3sas_con...t_number_pds(9)
β¨ mpt3sas_config_get_number_pds π
okay so bestie, welcome to the Kernel API Manual β this page is literally the whole vibe check for mpt3sas_config_get_number_pds, and i promise it's not as scary as the name looks π«Ά
πΈ NAME πΈ
mpt3sas_config_get_number_pds β obtain number of phys disk assigned to volume β¨
like, you give it a volume, it tells you how many physical disks are linked to it. that's the whole gig. no cap π
π SYNOPSIS π
int mpt3sas_config_get_number_pds (struct MPT3SAS_ADAPTER *ioc , u16
handle , u8 *num_pds );
so yeah. three args, returns an int, iconic behaviour π
π¦ ARGUMENTS π¦
iocβ per adapter object π this is your adapter baddie, the main character.handleβ volume handle π the specific volume we're asking about.num_pdsβ returns pds count β¨ note the "returns" β this one's the output, it gets filled in for you, iykyk.
π΄ CONTEXT π΄
sleep.
periodt. it's a sleepy girl π€ β call it in a context where sleeping is allowed, fr fr.
π₯ RETURN π₯
0 for success, non-zero for failure. that's it, that's the tea π
π SEE ALSO π
okay this list is LONG, so buckle up bestie β every single one, in order, no skipping π
- Kernel file
./drivers/scsi/mpt3sas/mpt3sas_config.c struct config_request(9)_config_display_some_debug(9)_config_alloc_config_dma_memory(9)_config_free_config_dma_memory(9)mpt3sas_config_done(9)_config_request(9)mpt3sas_config_get_manufacturing_pg0(9)mpt3sas_config_get_manufacturing_pg1(9)mpt3sas_config_get_manufacturing_pg10(9)mpt3sas_config_get_manufacturing_pg11(9)mpt3sas_config_set_manufacturing_pg11(9)mpt3sas_config_get_bios_pg2(9)mpt3sas_config_get_bios_pg3(9)mpt3sas_config_set_bios_pg4(9)mpt3sas_config_get_bios_pg4(9)mpt3sas_config_get_iounit_pg0(9)mpt3sas_config_get_iounit_pg1(9)mpt3sas_config_set_iounit_pg1(9)mpt3sas_config_get_iounit_pg3(9)mpt3sas_config_get_iounit_pg7(9)mpt3sas_config_get_iounit_pg8(9)mpt3sas_config_get_ioc_pg8(9)mpt3sas_config_get_ioc_pg1(9)mpt3sas_config_set_ioc_pg1(9)mpt3sas_config_get_sas_device_pg0(9)mpt3sas_config_get_pcie_device_pg0(9)mpt3sas_config_get_pcie_iounit_pg1(9)mpt3sas_config_get_pcie_device_pg2(9)mpt3sas_config_get_number_hba_phys(9)mpt3sas_config_get_sas_iounit_pg0(9)mpt3sas_config_get_sas_iounit_pg1(9)mpt3sas_config_set_sas_iounit_pg1(9)mpt3sas_config_get_expander_pg0(9)mpt3sas_config_get_expander_pg1(9)mpt3sas_config_get_enclosure_pg0(9)mpt3sas_config_get_phy_pg0(9)mpt3sas_config_get_phy_pg1(9)mpt3sas_config_get_raid_volume_pg1(9)mpt3sas_config_get_raid_volume_pg0(9)mpt3sas_config_get_phys_disk_pg0(9)mpt3sas_config_get_driver_trigger_pg0(9)_config_set_driver_trigger_pg0(9)mpt3sas_config_update_driver_trigger_pg0(9)mpt3sas_config_get_driver_trigger_pg1(9)_config_set_driver_trigger_pg1(9)mpt3sas_config_update_driver_trigger_pg1(9)mpt3sas_config_get_driver_trigger_pg2(9)_config_set_driver_trigger_pg2(9)mpt3sas_config_update_driver_trigger_pg2(9)mpt3sas_config_get_driver_trigger_pg3(9)_config_set_driver_trigger_pg3(9)mpt3sas_config_update_driver_trigger_pg3(9)mpt3sas_config_get_driver_trigger_pg4(9)_config_set_driver_trigger_pg4(9)mpt3sas_config_update_driver_trigger_pg4(9)mpt3sas_config_get_volume_handle(9)mpt3sas_config_get_volume_wwid(9)
go read those, bestie, they're all eating π
ngl the section list on this page stops at SEE ALSO β there's no OPTIONS, no EXAMPLES, no BUGS, no AUTHOR block hiding at the bottom. that's the whole menu, no crumbs left π
and that's the page!! mwah π this little number lives in ./drivers/scsi/mpt3sas and it's dated October 2026 β so yeah, she's from the future, main character energy only πβ¨ππ¦π
π¦ 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