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

✨ PROBE::NFS.AOP.WRITEPAGES ✨

okay bestie, welcome to the Network File Storage Tapsets corner of the 3stap manuals — this is the probe that catches your NFS client being a whole busy bee, writing several dirty pages at once over to the NFS server 💅

---

🌸 NAME 🌸

probe::nfs.aop.writepages — NFS client writing several dirty pages to the NFS server 🦋

---

🎀 SYNOPSIS 🎀

probe nfs.aop.writepages {}

that's it. that's the whole vibe. she's a probe, she takes no arguments, she just shows up 🔥

---

💖 VALUES 💖

every one of these is a lil variable you can read inside the probe handler, no cap:

• ino — the inode number. her government name 🪪
• size — how many pages got attempted to be written in this execution. the attempt count, bestie 💫
• for_reclaim — a flag of writeback_control, and it tells you if this was invoked from the page allocator 👀
• for_kupdate — also a flag of writeback_control, this one says whether it's a kupdate writeback ⭐
• wpages — write size, measured in pages 📄
• dev — device identifier 🍓
• wsize — write size 📏
• nr_to_write — number of pages attempted to be written in this execution 🧚

lowkey notice size and nr_to_write are described the same way? yeah. the manpage said it, so I said it. not my business, I just report 💀

---

🌈 DESCRIPTION 🌈

The priority of wb is decided by the flags for_reclaim and for_kupdate. that's the whole tea 🫖 those two flags are the main characters here, they literally decide what priority wb gets. periodt 👑

---

👑 SEE ALSO 👑

• tapset::nfs(3stap) — go read this one too, iykyk 💜

---

and that's a wrap, gorgeous 🌸 this was the SystemTap Tapset Reference, version-wise it's the Ver line, dated September 2026 — yeah, from the future, iconic behavior honestly 🕰️✨ go forth and trace those writepages, bestie, you're gonna slay 💖🦋🎀