PROBE::IOSCHEDULER.ELV_ADD_REQUEST.KP(3stap)

✨ NAME ✨

okay so probe::ioscheduler.elv_add_request.kp β€” it's a kprobe based probe (iykyk) that literally just tells you a request got added to the request queue. that's it. that's the whole vibe. it's in section 3stap of the manual, bestie πŸ’–


🌸 SYNOPSIS 🌸

probe ioscheduler.elv_add_request.kp {}

no arguments, no fancy setup, she just exists and reports things. iconic behavior honestly πŸ’…


πŸ¦‹ VALUES πŸ¦‹

every value this probe hands you, no cap, in order:

  • elevator_name β€” the type of I/O elevator that's currently enabled. yeah, the elevator. in your kernel. she's got range πŸ›—βœ¨
  • disk_minor β€” the disk minor number of the request πŸŽ€
  • rq_flags β€” the request flags, aka the little metadata receipts of the request 🧾
  • name β€” the name of the probe point. yes, she knows her own name, main character energy fr πŸ‘‘
  • q β€” a pointer to the request queue 🫢
  • rq β€” the address of the request πŸ“
  • disk_major β€” the disk major number of the request πŸ’œ
lowkey these are just the values you can grab inside your probe body β€” nothing spooky, just data. no cap.

🌈 SEE ALSO 🌈


okay and that's the page!! this was the SystemTap Tapset Reference, Ver (yes the version field is just vibing there empty, we don't question her), dated September 2026 πŸ—“οΈπŸ’– stay curious, stay probing, and remember: every request deserves to be seen. bye bestie πŸ¦‹πŸ’…πŸŽ€

πŸ“¦ where this page comes from