PROBE::NFS.PROC.(3stap)

πŸ’– probe::nfs.proc.read_setup β€” from the Network File Storage Tapsets (that's the 3stap manual, bestie) πŸ’–

🌸 NAME 🌸

probe::nfs.proc.read_setup β€” ok so this is the NFS client setting up a read RPC task. Just setting it up, not doing it. We'll get there. 🫢


✨ SYNOPSIS ✨

probe nfs.proc.read_setup {}

That's it. No args. She takes nothing and gives everything. πŸ‘‘


πŸŽ€ VALUES πŸŽ€

These are the lil variables you get to peek at inside the probe. Collect them like stickers. πŸ¦‹

  • server_ip β€” the IP address of the server, aka where the good stuff lives πŸ“
  • size β€” read bytes in this execution 🌸
  • count β€” read bytes in this execution 🌸 (yes bestie, same energy as size, they're both telling you about read bytes in this execution, I don't make the rules)
  • offset β€” the file offset, i.e. where in the file we're looking πŸ‘€
  • version β€” the NFS version πŸ’…
  • prot β€” the transfer protocol, the vibe of how the bytes travel 🌈

πŸ’… DESCRIPTION πŸ’…

So the read_setup function is literally there to setup a read RPC task. That's its whole job. Its entire personality.

And here's the important part, don't skip it: it is not doing the actual read operation. It's giving setup, not results. The main character is getting ready, she is not yet on stage. No cap. 🎭

Fr fr, if you came here expecting the actual read to happen β€” wrong probe, bestie. This one's just the prep era. πŸ’€

🌟 SEE ALSO 🌟


SystemTap Tapset Reference β€” September 2026 edition, mwah πŸ’‹ thanks for reading my lil tapset TED talk, go write some probes and slay πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«ΆπŸ‘‘πŸŒˆβ­

πŸ“¦ where this page comes from