mpt3sas_setup_direct_io(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 the scsi_cmnd command object. the actual SCSI command that wants to go do stuff ✨
  • raid_device β€” pointer to the _raid_device data structure. that's where the raid device info lives πŸ“
  • mpi_request β€” pointer to the SCSI_IO reqest 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 🫢

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