From: Eric Valette <eric.valette@free.fr>
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Inconsistancies in /proc (status vs statm) leading to wrong documentation (proc.txt)
Date: Sat, 09 Oct 2004 16:08:23 +0200 [thread overview]
Message-ID: <4167F0D7.3020502@free.fr> (raw)
In-Reply-To: <1097329771.2674.4036.camel@cube>
Albert Cahalan wrote:
> The documentation is incorrect. It was written to match a buggy
> implementation in early 2.6.x kernels.
Well the Documentation is said to matches 2.6.8-rc3 and is only 5 weeks
old according to bitkeeper changesets... So at least the doc should be
fixed.
> VmSize is the address space occupied, excluding memory-mapped IO.
> The statm value is the address space occupied.
Why removing memory-mapped IO in one case (status) and not the other
(statm)? Memory mapped IO, may of course reserve some physical memory
pages for establishing the mmu->phys adress translation table (if any)
but not really the amount of space mapped.
>>May I suggest :
>> - To use consistent memory size units between status and statm,
> No way. This would instantly break the "top" program.
OK. Too bad because statm is hardly readable but I guess it is not for
human then...
Thanks for responding,
-- eric
next prev parent reply other threads:[~2004-10-09 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 13:49 Inconsistancies in /proc (status vs statm) leading to wrong documentation (proc.txt) Albert Cahalan
2004-10-09 14:08 ` Eric Valette [this message]
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=4167F0D7.3020502@free.fr \
--to=eric.valette@free.fr \
--cc=albert@users.sf.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox