blk_rq_passthrough_stats(9)

💅 blk_rq_passthrough_stats(9) — the manual page, but make it make sense

okay so you found blk_rq_passthrough_stats in section 9 of the Kernel API Manual — bestie, welcome, this one is short and sweet and honestly kind of a vibe. Let's get into it 🫶

---

✨ NAME ✨

blk_rq_passthrough_stats — check if this request should account stats 🧮

Like literally, it's a yes/no vibe check on whether a request gets to be counted.

---

🌸 SYNOPSIS 🌸

bool blk_rq_passthrough_stats (struct request *rq , struct request_queue
*q );

That's it. Two args, one bool out. Clean. Iconic. No cap. 💅

---

🎀 ARGUMENTS 🎀

• rq — the request you're checking 👀 (you know, the one you're wondering about)
• q — the queue that's accumulating the stats 📊 (she's the one doing the counting)

---

🦋 DESCRIPTION 🦋

Okay so here's the one (1) thing you need to internalize, and it's lowkey important:

Note, q does not necessarily need to be the request_queue that provides rq. 🫠

Read that again. I'll wait. q and rq are not required to be each other's people — the queue collecting the stats doesn't have to be the same queue that handed you the request. So don't go assuming they're a matched set, bestie. That's the whole trick. 🙈

---

⭐ RETURN ⭐

Returns true if stats should be accounted. ✅

That's the entire answer. true = count it. No ambiguity, no cliffhanger, we love a straightforward return. 💖

---

🌈 SEE ALSO 🌈

Kernel file ./include/linux/blk-mq.h, plus the whole friend group:

• enum blk_eh_timer_return(9)
• struct blk_mq_hw_ctx(9)
• struct blk_mq_queue_map(9)
• enum hctx_type(9)
• struct blk_mq_tag_set(9)
• struct blk_mq_queue_data(9)
• struct blk_mq_ops(9)
• blk_mq_rq_state(9)
• blk_mq_add_to_batch(9)
• blk_mq_rq_from_pdu(9)
• blk_mq_rq_to_pdu(9)
• blk_rq_nr_bvec(9)

Go read those if you're nosy. I support it. 👑

---

and that's the page!! 🎉 sourced from ./include/linux, dated October 2026 — mwah, go forth and count your stats correctly, bestie 🧚💜