PROBE::IOSCHEDULER_TRACE.ELV_COMPLETED_REQUEST(3stap)

πŸ‘‘ NAME πŸ‘‘

probe::ioscheduler_trace.elv_completed_request β€” bestie, this tap fires when a request is... checks notes ...yeah the page literally cuts off there, that's all it says, and honestly? iconic of it. πŸ’…


✨ SYNOPSIS ✨

probe ioscheduler_trace.elv_completed_request {}

That's it. No arguments, no drama, just vibes. 🫢


🌸 VALUES 🌸

Okay so when this probe goes off, here's everything it hands you, no cap:

  • disk_minor β€” the disk's minor number for that request. baby number. the little one. πŸ“
  • elevator_name β€” which type of I/O elevator is currently enabled. yes it's really called an elevator, yes it's giving ✨main character✨, we move on. πŸ”₯
  • name β€” the name of the probe point. it knows its own name. self-aware queen. πŸ‘‘
  • rq_flags β€” the request's flags. 🚩 (the literal kind, not the situationship kind, chill)
  • rq β€” the address of the request. like a home address but for one (1) request. 🏠
  • disk_major β€” the disk's major number for that request. the big sibling number. πŸ’œ

πŸ’– DESCRIPTION πŸ’–

The whole description, verbatim energy, is:

completed.

That's the entire thing. The manpage said "completed." and then just left. 😭 Not me reading it three times looking for the rest of the sentence. It's not there, bestie. It's not there. What we can tell you is right there in the NAME section: this probe fires when a request is β€” and then the sentence simply stops existing. We respect the mystery. πŸ™ˆ


πŸŽ€ SEE ALSO πŸŽ€


SystemTap Tapset Reference, Ver September 2026. That's the manual, that's the version, that's the date, and that's the whole page. slay, go tap something. πŸ’…βœ¨πŸ§š

πŸ“¦ where this page comes from