From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: eric.valette@free.fr
Subject: Re: Inconsistancies in /proc (status vs statm) leading to wrong documentation (proc.txt)
Date: 09 Oct 2004 09:49:32 -0400 [thread overview]
Message-ID: <1097329771.2674.4036.camel@cube> (raw)
Eric Valette writes:
> I'm currently trying use mlockall for a soft RT application and was
> concerned by the memory usage of my (big) RT process. So I stated to
> look at /proc/<PID>/status and /proc/<PID>/statm and then to the
> documentation of statm (Documentation/filesystem/proc.txt) because
> unexplained values are rather useless.
>
> The doc currently says :
> -------------------------------------------------------------------------
> Field Content
> size total program size (pages) (same as VmSize in status)
The documentation is incorrect. It was written to match a buggy
implementation in early 2.6.x kernels.
VmSize is the address space occupied, excluding memory-mapped IO.
The statm value is the address space occupied.
> May I suggest :
> - To use consistent memory size units between status and statm,
No way. This would instantly break the "top" program.
next reply other threads:[~2004-10-09 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 13:49 Albert Cahalan [this message]
2004-10-09 14:08 ` Inconsistancies in /proc (status vs statm) leading to wrong documentation (proc.txt) Eric Valette
2004-10-09 16:31 ` Albert Cahalan
2004-10-09 16:46 ` Eric Valette
2004-10-09 16:59 ` Albert Cahalan
2004-10-09 17:46 ` Eric Valette
-- strict thread matches above, loose matches on Subject: below --
2004-10-09 9:54 Eric Valette
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=1097329771.2674.4036.camel@cube \
--to=albert@users.sf.net \
--cc=eric.valette@free.fr \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.