I'm creating a plugin for Munin to monitor stats of named processes. One of the sources of information would be /proc/[pid]/io
. But I have a hard time finding out what the difference is between rchar
/wchar
and read_bytes
/written_bytes
.
They are not the same, as they provide different values. What do they represent?
It corresponds to the /proc/[pid]/task/[tid]/path. Which seems to be what you are looking for. After your hints, I get the answer: on Linux, thread is actually a process, so /proc/[tid]/stack will get the thread's kernel stack info, or use /proc/[pid]/task/[tid]/stack .
The /proc/PID/maps file contains the currently mapped memory regions and their access permissions. or if empty, the mapping is anonymous.
/proc file system is a mechanism provided, so that kernel can send information to processes. This is an interface provided to the user, to interact with the kernel and get the required information about processes running on the system.
While the proc manpage is woefully behind (and so are most manpages/documentation on anything not relating to cookie-cutter user-space development), this stuff is fortunately documented completely in the Linux kernel source under Documentation/filesystems/proc.rst
. Here are the relevant bits:
rchar ----- I/O counter: chars read The number of bytes which this task has caused to be read from storage. This is simply the sum of bytes which this process passed to read() and pread(). It includes things like tty IO and it is unaffected by whether or not actual physical disk IO was required (the read might have been satisfied from pagecache) wchar ----- I/O counter: chars written The number of bytes which this task has caused, or shall cause to be written to disk. Similar caveats apply here as with rchar. read_bytes ---------- I/O counter: bytes read Attempt to count the number of bytes which this process really did cause to be fetched from the storage layer. Done at the submit_bio() level, so it is accurate for block-backed filesystems. <please add status regarding NFS and CIFS at a later time> write_bytes ----------- I/O counter: bytes written Attempt to count the number of bytes which this process caused to be sent to the storage layer. This is done at page-dirtying time.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With