From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: linux-mm@vger.kernel.org, rl@hellgate.ch, wli@holomorphy.com
Subject: Re: [proc.txt] Fix /proc/pid/statm documentation
Date: 05 Aug 2004 21:11:52 -0400 [thread overview]
Message-ID: <1091754711.1231.2388.camel@cube> (raw)
Roger Luethi writes:
> I really wanted /proc/pid/statm to die [1] and I still believe the
> reasoning is valid. As it doesn't look like that is going to happen,
It would be awful to lose statm, especially since WLI has fixes
for some of the problems. Just why do you want to kill statm?
Now quoting from your patch...
+ size total program size (pages) (same as VmSize in status)
+ resident size of memory portions (pages) (same as VmRSS in status)
There was a distinction here that has been lost. One of these
included memory-mapped hardware. You could see this with the
X server video memory.
For "top" running on a 2.2.xx or 2.4.xx kernel, the statm values
are better. Jim Warner determined this after careful examination,
and I have no desire to re-analyse the matter. Remember that user
tools are expected to run on both old and new kernels, while the
kernel is expected to support old apps. We call this an ABI...
+ shared number of pages that are shared (i.e. backed by a file)
This isn't in the status file. It's shown in top's default output.
Since top must read this value from statm, it might as well use
other parts of statm as well.
+ trs number of pages that are 'code' (not including libs; broken,
+ includes data segment)
Perhaps this works OK with the NX bit or on an Alpha? On a regular
i386 box, code and read-only data are pretty much the same.
Note: trs means "text RESIDENT set".
+ lrs number of pages of library (always 0 on 2.6)
This worked for a.out executables. (that 0x60000000 value is an
a.out constant) Oh well, trs will do.
+ drs number of pages of data/stack (including libs; broken,
+ includes library text)
Note: trs means "data RESIDENT set".
+ dt number of dirty pages (always 0 on 2.6)
This one would be useful.
These would be really useful too:
1. swap space used
2. swap space that would be used if fully paged out
For the pmap command, it would be nice to have per-mapping
values in the /proc/*/maps files. (resident, locked,
dirty, C-O-W, swapped...)
next reply other threads:[~2004-08-06 3:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 1:11 Albert Cahalan [this message]
2004-08-06 3:48 ` [proc.txt] Fix /proc/pid/statm documentation William Lee Irwin III
2004-08-06 9:40 ` Roger Luethi
2004-08-06 10:46 ` William Lee Irwin III
2004-08-06 12:01 ` Roger Luethi
2004-08-06 12:11 ` William Lee Irwin III
2004-08-06 13:57 ` Roger Luethi
2004-08-06 14:07 ` William Lee Irwin III
2004-08-06 15:02 ` Roger Luethi
2004-08-06 14:02 ` Albert Cahalan
2004-08-06 17:08 ` Roger Luethi
2004-08-06 15:14 ` Albert Cahalan
2004-08-06 20:49 ` Martin J. Bligh
2004-08-06 18:38 ` Albert Cahalan
2004-08-06 21:15 ` Martin J. Bligh
2004-08-07 17:37 ` Paul Jackson
2004-08-06 12:58 ` Albert Cahalan
2004-08-06 15:48 ` William Lee Irwin III
2004-08-06 14:14 ` Albert Cahalan
2004-08-06 16:49 ` William Lee Irwin III
2004-08-06 16:34 ` Roger Luethi
2004-08-06 14:51 ` Albert Cahalan
2004-08-06 17:28 ` Martin J. Bligh
2004-08-06 18:21 ` Roger Luethi
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 17:10 Roger Luethi
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=1091754711.1231.2388.camel@cube \
--to=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=rl@hellgate.ch \
--cc=wli@holomorphy.com \
/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