PROBE::NFS.AOP.W(3stap)

✨ PROBE::NFS.AOP.WRITEPAGE ✨

okay so this is a page from the Network File Storage Tapsets section of the SystemTap Tapset Reference β€” the manual is PROBE::NFS.AOP.W(3stap), section 3stap, and bestie, it's literally about watching your NFS client yeet a mapped page over to the NFS server. πŸ’…


🌸 NAME 🌸

probe::nfs.aop.writepage β€” NFS client writing a mapped page to the NFS server. that's the whole vibe. πŸ¦‹


✨ SYNOPSIS ✨

probe nfs.aop.writepage {}

no args, no drama, just the probe. πŸŽ€


πŸ‘‘ VALUES πŸ‘‘

bestie these are the little goodies you get to peek at inside the probe. every single one, no skips:

  • i_size β€” the file length, in bytes. πŸ“
  • ino β€” the inode number. it's giving who is this file energy. πŸ”
  • sb_flag β€” the super block flags. βš‘
  • for_kupdate β€” a flag of writeback_control, and it tells you if this is a kupdate writeback. 🧚
  • for_reclaim β€” also a flag of writeback_control, this one tells you if it got invoked from the page allocator. ♻️
  • size β€” how many pages are getting written in this execution. πŸ“š
  • page_index β€” offset within the mapping; you can use it as a page identifier and as a position identifier in the page frame. double duty, iconic. 🫢
  • i_flag β€” the file flags. 🚩
  • __page β€” the address of the page. πŸ“
  • i_state β€” the inode state flags. 🌈
  • dev β€” the device identifier. πŸ’Ύ
  • wsize β€” the write size. ✍️

πŸ’– DESCRIPTION πŸ’–

The priority of wb is decided by the flags for_reclaim and for_kupdate. that's the tea, that's the whole mechanic. πŸ“


πŸ”₯ SEE ALSO πŸ”₯


and that's the page, bestie!! this was the SystemTap Tapset Reference, version, dated September 2026 β€” so if you're reading this from the future, hiii, hope the NFS writeback is treating you gently. πŸ’œβœ¨ periodt. πŸŽ€πŸ¦‹πŸ’…

πŸ“¦ where this page comes from