From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: linux-mm@kvack.org, Mel Gorman <mel@csn.ul.ie>, acahalan@cs.uml.edu
Subject: Synchronization of the procps tools with /proc/meminfo
Date: Mon, 18 Feb 2008 16:55:58 +0100 [thread overview]
Message-ID: <e2e108260802180755l1c80b13an89ed417c20132f08@mail.gmail.com> (raw)
As known the tools in the procps package (e.g. top and free) obtain
their status information from the Linux kernel by reading a.o.
/proc/meminfo. Both top and free report a.o. the following
information:
* Total amount of physical memory.
* Physical memory in use (reclaimable + unreclaimable).
* Unreclaimable physical memory.
Current versions of the procps tools only take "Buffers" and "Cached"
in account as reclaimable memory and ignore the SReclaimable field
(slab reclaimable, includes a.o. the memory occupied by dentry and
inode structures), one of the more recently added /proc/meminfo field
(the latest procps release (version 3.2.7) dates from June 25, 2006).
I would like to see both top and free modified such that these take
the SReclaimable field in account. The reason is that the numbers
reported by free as "-/+ buffers/cache" are useless on recent kernels
when monitoring a Linux system for memory leaks in kernel and/or
server processes. E.g. when findutils updates its database, a lot of
extra dentry and inodes are cached. The output of "free" shows a
significant increase in the amount of memory used, while only
SReclaimable increased and not the unreclaimable physical memory.
This leads me to the question: if the layout of /proc/meminfo changes,
who communicates these changes to the procps maintainers ? And who
maintains the procps package ? I have tried before to contact Albert
Calahan but without success so far.
See also:
* The procps package -- http://procps.sourceforge.net/
* A previous attempt to inform the procps maintainers:
http://sourceforge.net/mailarchive/forum.php?thread_name=e2e108260802132333w4459ae23o3a5930583f426339%40mail.gmail.com&forum_name=procps-feedback
Bart Van Assche.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2008-02-18 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 15:55 Bart Van Assche [this message]
2008-02-19 18:53 ` Synchronization of the procps tools with /proc/meminfo Albert Cahalan
2008-02-19 18:59 ` Bart Van Assche
2008-03-08 9:35 ` Bart Van Assche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2e108260802180755l1c80b13an89ed417c20132f08@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=acahalan@cs.uml.edu \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).