Thanks. Here is the output. Pmap looks the same on both (2.4 and 2.6), so top/VIRT on 2.4 is not accurate. Can I derive from this output the real physical memory in use?
[root@testvx root]# pmap -x 27977
27977: winmed_v15.26 -I194.0.0.250 -NPAULM-XP -S5 -P11401 -R2 -TSun_May_07_09
:23:55_2006434 -B15
Address Kbytes RSS Anon Locked Mode Mapping
08048000 26824 - - - r-x-- winmed_v15.26
09a7a000 512 - - - rw--- winmed_v15.26
09afa000 11368 - - - rwx-- [ anon ]
40007000 40 - - - r-x-- libnss_files-2.3.2.so
40011000 4 - - - rw--- libnss_files-2.3.2.so
40012000 1160 - - - r-x-- libc-2.3.2.so
40134000 24 - - - rw--- libc-2.3.2.so
4013a000 8 - - - rw--- [ anon ]
4013c000 72 - - - r-x-- ld-2.3.2.so
4014e000 4 - - - rw--- ld-2.3.2.so
bffed000 76 - - - rwx-- [ stack ]
-------- ------- ------- ------- -------
total kB 40092 - - -
Main Topics
Browse All Topics





by: DonConsolioPosted on 2006-05-08 at 19:15:41ID: 16635927
try using pmap to get "real" memory usage info.
e.g.
# pmap -d PID_OF_PROCESS
Address Kbytes Mode Offset Device Mapping
08048000 456 r-x-- 0000000000000000 068:00001 bash
080ba000 12 rw--- 0000000000071000 068:00001 bash
[...]
bfffa000 24 rw--- 00000000bfffa000 000:00000 [ stack ]
ffffe000 4 ----- 0000000000000000 000:00000 [ anon ]
mapped: 3096K writeable/private: 612K shared: 24K