mpt3sas_setup_direct_io(9)
π mpt3sas_setup_direct_io(9) β from the Kernel API Manual, bestie
okay so you found a 9-section page, meaning it's kernel API tea, and this one is mpt3sas_setup_direct_io β the function that sets up the MPI request for WARPDRIVE Direct I/O. yes. WARPDRIVE. it's giving fast lane energy and we're obsessed π₯
β¨ NAME β¨
mpt3sas_setup_direct_io β setup MPI request for WARPDRIVE Direct I/O π¦
πΈ SYNOPSIS πΈ
void mpt3sas_setup_direct_io (struct MPT3SAS_ADAPTER *ioc , struct
scsi_cmnd *scmd , struct _raid_device *raid_device ,
Mpi25SCSIIORequest_t *mpi_request );
like, exactly that. four args, void return, no cap π
(it's a void function so don't go looking for a return value, there isn't one!)
π ARGUMENTS π
iocβ the per adapter object. your adapter's whole personality, basically. main character energy πscmdβ pointer to thescsi_cmndcommand object. the actual SCSI command that wants to go do stuff β¨raid_deviceβ pointer to the_raid_devicedata structure. that's where the raid device info lives πmpi_requestβ pointer to theSCSI_IOreqest message frame. and yes, "reqest" is spelled like that in the original and I am not fixing it, we respect the source ππ
ngl bestie, the arg one-liners are literally the whole map here β per adapter, the scsi command, the raid device struct, and the message frame. that's it. that's the vibe check π
π«Ά SEE ALSO π«Ά
- Kernel file
./drivers/scsi/mpt3sas/mpt3sas_warpdrive.cβ yeah the source file is in SEE ALSO, that's just how this page does it π _warpdrive_disable_ddio(9)mpt3sas_get_num_volumes(9)mpt3sas_init_warpdrive_properties(9)
go read those next, iykyk π the whole warpdrive squad is right there β
and that's the page, bestie π§ this one came out of ./drivers/scsi/mpt3sas with the date October 2026, filed under mpt3sas_setup_direct_io(9) β slay, periodt π
π¦ 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