STRUCT BFQ_IO_CQ(9)

🦋 struct bfq_io_cq(9) 🦋

okay so bestie, welcome to the Kernel API Manual page for struct bfq_io_cq, and no cap, this one is a whole vibe — it's the little bookkeeping struct that lives at the intersection of a request_queue and an io_context. Periodt. 💅

---

✨ NAME ✨

struct bfq_io_cq — the per (request_queue, io_context) structure. that's it, that's the whole personality. she's a pair-bonded queen. 👑

---

🌸 SYNOPSIS 🌸

here's the shape of her, literally copy-pasted from the source of truth:

struct bfq_io_cq {
    struct io_cq icq;
    struct bfq_queue *bfqq[2][BFQ_MAX_ACTUATORS];
    int ioprio;
  #ifdef CONFIG_BFQ_GROUP_IOSCHED;
    uint64_t blkcg_serial_nr;
  #endif;
    struct bfq_iocq_bfqq_data bfqq_data[BFQ_MAX_ACTUATORS];
    unsigned int requests;
 };

look at her. the little icq on top like a crown 🎀, the two-dimensional bfqq[2][BFQ_MAX_ACTUATORS] array doing the absolute most, ioprio keeping things prioritized, and then <pink>blkcg_serial_nr</pink> tucked away behind #ifdef CONFIG_BFQ_GROUP_IOSCHED — she only shows up when group I/O scheduling is compiled in, and honestly? conditional icon behavior. 🫶

and don't sleep on the trailing semicolons after #ifdef and #endif — those are in the original and we are not touching them, that's not our business. 💀

---

💜 Members 💜

so the Members section on this page is, um… empty. like, genuinely nothing under it. no bullets, no descriptions, no members. it's giving minimalist. it's giving "the members are up in the SYNOPSIS, girl, go look."

which like — fair — because every single member is right up there in the synopsis: icq, bfqq, ioprio, blkcg_serial_nr, bfqq_data, and requests. no extra lore beyond that on this page, and I'm not about to make any up. 🧚

---

🔥 SEE ALSO 🔥

the kernel file that actually owns this whole situation:

• ./block/bfq-iosched.h

and the whole friend group of related structs, all in (9):

• struct bfq_service_tree(9)
• struct bfq_sched_data(9)
• struct bfq_weight_counter(9)
• struct bfq_entity(9)
• struct bfq_ttime(9)
• struct bfq_queue(9)
• struct bfq_data(9)
• struct bfq_group(9)

go read them, they all ate. 🌈

---

ngl, if you're here for a deep dive into each member's behavior, this page is a short one — the whole synopsis is the content. don't go inventing semantics, bestie, the manual didn't say. 💀

---

mwah, that's the page! 💖 this little love letter was served fresh from ./block, dated October 2026, and yes, the footer says struct bfq_io_cq(9) again because she loves a callback. see you in the next (9) page, iykyk. 🌸🦋✨