STRUCT CONFIG_REQUEST(9)

💖 NAME 💖

okay so bestie, welcome to struct config_request(9) — a page straight from the Kernel API Manual and it is literally about how to obtain dma memory via routine. That's the whole vibe. It's giving “obtain dma memory via routine” and nothing else, and honestly? Slay. 💅✨

🦋 SYNOPSIS 🦋

Here's the struct in all its main-character glory — copy it exactly, bestie, don't improvise:

struct config_request {
    u16 sz;
    void *page;
    dma_addr_t page_dma;
 };

🌸 Members 🌸

okay so the members are lowkey simple and highkey iconic:

• sz — the size. That's it. Just size. 💖
• page — virt pointer. Virtual pointer energy, periodt. ✨
• page_dma — phys pointer. Physical pointer vibes, no cap. 🦋

✨ SEE ALSO ✨

Kernel file first, because bestie, that's where the lore lives: ./drivers/scsi/mpt3sas/mpt3sas_config.c 💅

Then the whole SEE ALSO squad — every single one, in order:

• _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_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)

okay that's the page, bestie. Source/version: ./drivers/scsi/mpt3sas, date: October 2026, and the page itself: struct config_request(9). Stay iconic, hydrate, and don't forget to vibe-check your pointers. 🫶💖✨