TAPSET::IOBLOCK(3stap)

πŸ¦‹ TAPSET::IOBLOCK β€” bestie edition πŸ’…

okay so this is a page from the SystemTap Tapset Reference, manual section 3stap, and it's literally called tapset::ioblock. it's the whole ioblock tapset, and it's short and iconic and we're gonna go through it together, fr fr. no cap. πŸŽ€


✨ NAME ✨

tapset::ioblock β€” the systemtap ioblock tapset πŸ‘‘


🌸 DESCRIPTION 🌸

so this tapset is all about block I/O, and it's giving five whole probe points. each one fires at a very specific lil moment in the life of a block I/O request, and each one has its own full breakdown living in a probe:: page that you should absolutely go read. here they are, one by one, no skips, no summaries. πŸ’–

🌈 ioblock.request

Fires whenever you're making a generic block I/O request. like, the moment the request goes out the door. πŸšͺ✨

For the full tea, see probe::ioblock.request(3stap).

🌈 ioblock.end

Fires whenever a block I/O transfer is complete. we love a finished transfer. we stan a finished transfer. 🫢

For the full tea, see probe::ioblock.end(3stap).

🌈 ioblock_trace.bounce

Fires whenever a buffer bounce is needed for at least one page of a block IO request. yes, "bounce", that's the real name, iykyk. 😭

For the full tea, see probe::ioblock_trace.bounce(3stap).

🌈 ioblock_trace.request

Fires just as a generic block I/O request is created for a bio. like right at the birth of it. main character energy. πŸ‘‘

For the full tea, see probe::ioblock_trace.request(3stap).

🌈 ioblock_trace.end

Fires whenever a block I/O transfer is complete. yep, same vibe as ioblock.end, different probe. both are valid. both are slaying. πŸ’…

For the full tea, see probe::ioblock_trace.end(3stap).


⭐ SEE ALSO ⭐

go read these too, bestie, they're all connected and they all ate:


and that's the whole page!! πŸ¦‹ SystemTap Tapset Reference, September 2026 β€” mwah, love u, go trace some block I/O, you've got this. πŸ’–πŸŒΈβœ¨

πŸ“¦ where this page comes from