PROBE::NFS.FOP.R(3stap)

πŸ’– PROBE::NFS.FOP.R πŸ’–

okay so this is a page from the Network File Storage Tapsets section of the SystemTap Tapset Reference, section 3stap, and it's all about one lil probe. bestie, we're talking probe::nfs.fop.read_iter β€” the NFS client read_iter file operation. it's giving "let me peek at what happens when somebody reads a file over NFS" ✨


🌸 NAME 🌸

probe::nfs.fop.read_iter β€” the NFS client read_iter file operation, periodt. that's the whole name, no notes πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

probe nfs.fop.read_iter {}

yep, that's it. no arguments, no fuss, just vibes. the probe takes an empty parameter list and she slays πŸŽ€


⭐ VALUES ⭐

these are all the values this probe hands you, and ngl every single one of them is important, so let's go one by one 🫢

  • attrtimeo β€” how long the cached info is assumed to be valid. we need to revalidate the cached attrs for this inode if jiffies - read_cache_jiffies > attrtimeo. so basically it's the "is my cache still trustworthy" deadline, and it matters 😭
  • dev β€” device identifier
  • ino β€” inode number
  • cache_valid β€” cache related bit mask flag
  • file_name β€” file name
  • pos β€” current position of file
  • parent_name β€” parent dir name
  • cache_time β€” when we started read-caching this inode
  • count β€” read bytes

lowkey a whole little receipt of what the read was doing πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

go read that one too, iykyk πŸ’œ


and that's the whole page bestie, no cap. this was SystemTap Tapset Reference, version Ver, dated September 2026 β€” shoutout to the September 2026 era for coming through with the docs πŸŒˆπŸŽ€πŸ’– bye ily, go read some NFS tapsets ✨

πŸ“¦ where this page comes from