trace_block_rq_remap(9)

📦 version 7.3.1, in nixpkgs unstable

✨ trace_block_rq_remap(9) ✨

okay so bestie, welcome to the Kernel API Manual 💅 this little cutie lives in the kernel tracing world and honestly? she's giving backstage-pass energy 🎀

🌸 NAME 🌸

trace_block_rq_remap — literally the tracepoint that maps a request for a block operation request 🦋

✨ SYNOPSIS ✨

void trace_block_rq_remap (struct request *rq , dev_t dev , sector_t
from );

no cap, that's the whole signature — she takes three things and returns void 💖

🎀 ARGUMENTS 🎀

  • rq — the block IO operation request, aka the main character of this whole situation 👑
  • dev — the device for the operation, like which stage this performance is happening on 🌈
  • from — the original sector for the operation, the before pic basically 🙈

💜 DESCRIPTION 💜

So here's the tea 🍓: the block operation request rq in q has been remapped. That's it, that's the vibe.

The block operation request rq holds the current information, and from holds the original sector — so you get the now and the then, both slaying in the same call 💫

🔥 SEE ALSO 🔥

Kernel file ./include/trace/events/block.h ✨ and like, the whole friend group honestly:

ngl bestie, q shows up in the description without getting its own argument slot — that's just how the original text rolls, so I'm passing the message along exactly as written 🫶

and that's the page!! sourced from ./include/trace/events, dated October 2026 — mwah, go forth and trace responsibly 💖✨🎀🦋🌸💅

📦 where this page comes from