mpt3sas_con...t_iounit_pg7(9)
β¨ mpt3sas_con...t_iounit_pg7(9) β¨
okay so bestie, we're in the Kernel API Manual today and this page is genuinely a little legend: mpt3sas_config_get_iounit_pg7. That truncated header is not a typo bestie, that's just how it's printed, iykyk π
πΈ NAME πΈ
mpt3sas_config_get_iounit_pg7 β obtain iounit page 7 π
like, that's literally the whole job. it gets you iounit page 7. slay.
π¦ SYNOPSIS π¦
int mpt3sas_config_get_iounit_pg7 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi2IOUnitPage7_t *config_page );
no cap, that's the whole signature. returns an int, takes three args. iconic.
π ARGUMENTS π
iocβ the per adapter object. your adapter's whole personality lives in here π«Άmpi_replyβ reply mf payload returned from firmware. yes "mf" is in the actual manpage, I'm not making this up, the kernel said it first πconfig_pageβ contents of the config page. this is where the page-7 goodness lands π
π΄ CONTEXT π΄
sleep.
that's it. that's the context. this function sleeps. the entire context section is the word "sleep" and honestly? mood. π
β RETURN β
0 for success, non-zero for failure. so like, check it. please check it. π
π₯ SEE ALSO π₯
the friend group is huge, this function knows literally everyone:
- 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_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_number_pds(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)
the way that list just keeps going... 58 entries and not one of them skipped, we respect the grind π
that's the whole page bestie, go get that iounit page 7 π
kisses from ./drivers/scsi/mpt3sas, dated October 2026, printed in the Kernel API Manual β stay slay, stay sleeping, and always check your return value πβ¨
π¦ 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