STRUCT ZFCP_QDIO(9)

💅 struct zfcp_qdio(9) — the manual page bestie

okay so picture this: you're deep in the s390 SCSI trenches and you need the kernel API manual for struct zfcp_qdio(9). that's literally this page. the function is called struct zfcp_qdio and it's described as the basic qdio data structure. no cap, that's the whole vibe. it's giving "foundational." it's giving "main character energy" for the qdio layer. let's get into it 🫶

---

✨ NAME ✨

struct zfcp_qdio — the basic qdio data structure. yes bestie, that's the entire name section. iconic minimalism.

---

🌸 SYNOPSIS 🌸

here's the struct in all its glory — copy it exactly, do not come for me about formatting:

struct zfcp_qdio {
    struct qdio_buffer      *res_q[QDIO_MAX_BUFFERS_PER_Q];
    struct qdio_buffer      *req_q[QDIO_MAX_BUFFERS_PER_Q];
    u8 req_q_idx;
    atomic_t req_q_free;
    spinlock_t stat_lock;
    spinlock_t req_q_lock;
    unsigned long long      req_q_time;
    u64 req_q_util;
    atomic_t req_q_full;
    wait_queue_head_t req_q_wq;
    struct tasklet_struct   irq_tasklet;
    struct tasklet_struct   request_tasklet;
    struct timer_list       request_timer;
    struct zfcp_adapter     *adapter;
    u16 max_sbale_per_sbal;
    u16 max_sbale_per_req;
 };

it's a lot of members, but every single one is doing its little job and we respect that 💖

---

🦋 DESCRIPTION 🦋

so this struct is the whole qdio situation for zfcp. it holds the response queue (res_q) and the request queue (req_q), plus all the bookkeeping that keeps those queues from going feral. there are counters, locks, timestamps, tasklets, a timer, a pointer back to the adapter, and some limits. it's basically the group chat admin of the driver — keeping everyone in line, tracking who said what when, and making sure nobody sends 400 messages at once.

let's meet the members one by one, because they all deserve their moment 👑

---

🎀 MEMBERS 🎀

the queues 💌

• res_q — the response queue. this is where the replies come back. the answer queue. the "omg she replied" queue.
• req_q — the request queue. this is where your outgoing stuff gets lined up. the "me sending the first text" queue.

the request-queue bookkeeping 📋

• req_q_idx — the index of next free buffer. it's literally pointing at the next open spot like "you can sit here bestie."
• req_q_free — the number of free buffers in queue. a little counter keeping track of how much room is left. when it hits zero, we have a problem 😭
• req_q_time — the time of last fill level change. a timestamp of the last time the queue's fullness shifted. it's giving "last seen" energy.
• req_q_util — used for accounting. that's literally what the manpage says. it's the numbers girlie. let her do her math 🧮
• req_q_full — the queue full incidents. a count of every time the queue was like "nope, full, try again." the drama counter. the "how many times did we hit the limit" tally.
• req_q_wq — the wait queue head. used to wait for SBAL availability. so when there's no SBAL to grab, this is where you wait. it's the literal waiting room. take a seat, bestie 🪑

the locks 🔒

• stat_lock — a spinlock whose whole job is to protect req_q_util and req_q_time. don't touch those two without holding this lock, iykyk.
• req_q_lock — a spinlock to serialize access to the request queue. one at a time, no cutting in line. periodt.

the tasklets and timer ⚡

• irq_tasklet — a struct tasklet_struct used for QDIO interrupt processing. this is the interrupt-handling tasklet. the "handle the interrupt, but make it deferred" queen.
• request_tasklet — a struct tasklet_struct used for Request Queue completion processing. this one is in charge of the request queue completion flow. the closer. the "we're done here" energy.
• request_timer — a struct timer_list used to trigger the Request Queue completion processing. it's the alarm clock that says "hey, go do the completion processing." very "rise and grind" of it ☀️

the adapter 🔌

• adapter — a struct zfcp_adapter * pointing to the adapter used in conjunction with this qdio structure. it's the back-reference. the "who do I belong to" pointer. the linked bestie.

the limits 📏

• max_sbale_per_sbal — a u16 holding the qdio limit per sbal. that's the cap, bestie. do not exceed.
• max_sbale_per_req — a u16 holding the qdio limit per request. another cap. another boundary. we stay within limits in this house.

---

🔥 SEE ALSO 🔥

if you want the full lore, go read the Kernel file ./drivers/s390/scsi/zfcp_qdio.h and also check out these iconic siblings:

struct zfcp_qdio_req(9), zfcp_qdio_sbale_req(9), zfcp_qdio_sbale_curr(9), zfcp_qdio_req_init(9), zfcp_qdio_fill_next(9), zfcp_qdio_set_sbale_last(9), zfcp_qdio_skip_to_last_sbale(9), zfcp_qdio_sbal_limit(9), zfcp_qdio_set_data_div(9), zfcp_qdio_real_bytes(9), zfcp_qdio_set_scount(9)

they're all linked in the header and they all slay in their own way 💅

---

quick vibe check: this is a kernel API manual page, so treat it like reference material — every member, every type, every lock description above is straight from the source. no invented behaviour, no extra tips, just facts with a glow-up ✨

---

and that's the page, bestie 🎀 this whole thing lives under ./drivers/s390/scsi and it's dated October 2026, so go forth and reference struct zfcp_qdio(9) with confidence. you're gonna do amazing. mwah 💖🦋🌸