csio_queuecommand(9)

💅 csio_queuecommand — a kernel API manual moment (section 9, bestie)

okay so like, welcome to the glow-up of csio_queuecommand(9) from the Kernel API Manual — she's the entry point that kicks off an I/O request and honestly? main character energy fr fr.

---

✨ NAME ✨

csio_queuecommand — the literal entry point to kickstart an I/O request. she starts the vibes, the hardware does the rest 🎀

---

🌸 SYNOPSIS 🌸

enum scsi_qc_status csio_queuecommand (struct Scsi_Host *host , struct
       scsi_cmnd *cmnd );

like, that's the whole signature, no cap. returns an enum scsi_qc_status, takes two args, slay.

---

🦋 ARGUMENTS 🦋

• host — the scsi_host pointer, iykyk. she's the host, she's holding it down 💖
• cmnd — the I/O request from ML. yes bestie, ML. that's where it came from 🫶

---

👑 DESCRIPTION 👑

so this routine right here? she does a lot. let's go through it because the way she's booked and busy is iconic:

• Checks for HW and Rnode module readiness — vibe check first, always ✨
• Gets a free ioreq structure (which is already initialized to uninit during its allocation — not me, that's just how she was born 💅)
• Maps SG elements
• Initializes ioreq members
• Kicks off the SCSI state machine for this IO — and yes she ate 🔥
• Returns busy status on error 😭 (it's giving "sorry bestie, not right now")

no skipping steps okay?? every single one of those is doing something. respect the pipeline 🙈

---

🧚 SEE ALSO 🧚

Kernel file ./drivers/scsi/csiostor/csio_scsi.c, plus her two besties csio_scsim_init(9) and csio_scsim_exit(9) — go say hi 🌈

---

and that's the page! brought to you by ./drivers/scsi/csiostor, dated October 2026, still serving csio_queuecommand(9) realness ⭐ bye bestie, go queue some commands 💜