sci_controller_complete_io(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sci_controller_complete_io(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes, the actual manual, and yes, I'm about to make a kernel function sound cute. strap in.


✨ NAME ✨

sci_controller_complete_io β€” this method will perform core specific completion operations for an IO request. After this method is invoked, the user should consider the IO request as invalid until it is properly reused (i.e. re-constructed).

🫢 lowkey important: once you call this, that ireq is done. not "done but maybe recyclable", not "done-ish". invalid. don't touch it until you've properly reused it (i.e. re-constructed it). that's not me being dramatic, that's literally the manpage.

✨ SYNOPSIS ✨

enum sci_status sci_controller_complete_io (struct isci_host *ihost ,
struct isci_remote_device *idev , struct isci_request *ireq );

three pointers, one enum sci_status back. she's giving "small signature, big responsibility" energy fr fr. πŸ’…


✨ ARGUMENTS ✨

  • ihost β€” the handle to the controller object for which to complete the IO request. your main character controller, basically πŸ‘‘
  • idev β€” the handle to the remote device object for which to complete the IO request. the remote device in question, we love her πŸ’–
  • ireq β€” the handle to the io request object to complete. yes, the very request you're about to declare invalid, no cap 🫢

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/isci/host.c β€” and the whole friend group, honestly:

like, go read them too, they're iconic in their own way πŸ¦‹


okay that's the whole thing, you ate that πŸ“ this came from ./drivers/scsi/isci, dated October 2026, and it's filed under sci_controller_complete_io(9) β€” mwah, bye bestie πŸ’œβœ¨

πŸ“¦ where this page comes from