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 19:46:14 +0200 [thread overview]
Message-ID: <416823E6.6020008@free.fr> (raw)
In-Reply-To: <1097341175.2669.4257.camel@cube>
Albert Cahalan wrote:
> Not quite, but close. Those that know are willing
> to read the kernel code, including that of past
> releases, can certainly use the statm file.
Sure but it while doing that after readding the official documentation
that the trouble began...
> For that, go directly to /proc/*/maps and be happy.
That's a good point. Very usefull for knowing which dynamic library
account for what size. I start wondering if dynamic libraries and
mlockall works well toghether..
> You may also want the RSS from /proc/*/status.
Well RSS = VmSize after mlockall I guess
Thanks for the maps hint,
-- eric
next prev parent reply other threads:[~2004-10-09 17:46 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
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 [this message]
-- 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=416823E6.6020008@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