Operating System - HP-UX
1840606 Members
4773 Online
110166 Solutions
New Discussion

verification of glance system memory report

 
SOLVED
Go to solution
Sam Miller_2
Occasional Advisor

verification of glance system memory report

Hi,

I have a HP-UX B.11.11 U 9000/800 box
with 32G of ram and glance displays :

Total VM : 11.8gb
Sys Mem : 18.4gb
User Mem: 10.1gb
Phys Mem: 32.0gb
Active VM: 8.22gb
Buf Cache: 24.1mb
Free Mem: 3.44gb

My understanding is that glance does not report on shared memory but ipcs reports 9G of shared memory segments.

Is there a way to verify if glance reports system memory correctly. It occurs to me that 18G would be too much. kmeminfo shows this:
Physical memory usage summary (in pages):

Physmem = 8381696 Available physical memory:
Freemem = 703833 Free physical memory
Used = 7677863 Used physical memory:
System = 186847 by kernel:
Static = 180548 for text and static data
Dynamic = 0 for dynamic data
Bufcache = 6162 for file-system buffer cache
Eqmem = 137 for equiv. mapped page pool
SCmem = 0 for system critical page pool
User = 2842564 by user processes
Uarea = 11408 for thread uareas
Disowned = 208950 disowned pages

----------------------------------------------------------------------
Dynamic memory usage summary (in pages):

Dynamic = 0 Kernel dynamic data (sysmap):
MALLOC = 0 memory buckets:
bucket[ 5] = 0 size 32 bytes
bucket[ 6] = 0 size 64 bytes
bucket[ 7] = 0 size 128 bytes
bucket[ 8] = 0 size 256 bytes
bucket[ 9] = 0 size 512 bytes
bucket[10] = 0 size 1024 bytes
bucket[11] = 0 size 2048 bytes
bucket[12] = 0 size 4096 bytes
bucket[13] = 0 size 2 pages
bucket[14] = 0 size 3 pages
bucket[15] = 0 size 4 pages
bucket[16] = 0 size 5 pages
bucket[17] = 0 size 6 pages
bucket[18] = 0 size 7 pages
bucket[19] = 0 size 8 pages
bucket[20] = 0 size > 8 pages
Kalloc = 0 kalloc()
Eqalloc = 0 eqalloc()
Reserved = 0 Reserved pools


I would appreciate your feedback,
Thanks!
7 REPLIES 7
Pete Randall
Outstanding Contributor

Re: verification of glance system memory report

To tell the amount of physical memory installed, run this little script:

# Note: For Itanium, use the following:
# echo "${MYSYMBOL}/jd" | adb $HPUX /dev/kmem
HPUX=/stand/vmunix
MAJORREV=$(uname -r | cut -f2 -d .)
if [ $MAJORREV -ge "11.0" ]
then
MYSYMBOL="phys_mem_pages"
else
MYSYMBOL="physmem"
fi

MYMEM=$(echo "${MYSYMBOL}/D" \
| adb $HPUX /dev/kmem \
| grep "${MYSYMBOL}: *." \
| awk '{printf "%.0f MB\n",$2/256}')
echo $MYMEM


Pete

Pete
Don Morris_1
Honored Contributor
Solution

Re: verification of glance system memory report

I distrust your kmeminfo, being that I can't comprehend a way for an 11.11 kernel to come up with no Dynamic allocations (I know of several unconditional ones just off the top of my head).

What version of kmeminfo are you using? Because your output makes me suspect that it predates ones that know about the Arena Allocator (instead of the old Bucket-style allocator) and that's why it's missing the system dynamic usage.
Sam Miller_2
Occasional Advisor

Re: verification of glance system memory report

kmeminfo:
kmeminfo.c Revision: 3.11, Date: 2000/12/07
kas.c Date: 2000/04/03 (support for PHKL_21532)
LIBP4: $Header: vers.c,v 5.17 2000/12/06 14:08:39 phi Exp $

I should have been more clear. I am interested in memory used by kernel, not memory installed in the system. I can verify memory installed on the system using stm.
Pete Randall
Outstanding Contributor

Re: verification of glance system memory report

Sorry, Sam. My misunderstanding.


Pete

Pete
Don Morris_1
Honored Contributor

Re: verification of glance system memory report

Yup, that kmeminfo is ancient and predates the Arena Allocator.

Get a later version from ftp://hprc.external.hp.com/memory.htm#kmeminfo and take another look.
Sam Miller_2
Occasional Advisor

Re: verification of glance system memory report

Will try. Thanks!

Is there any way to see how much memory is taken by loadable kernel modules?

The symptoms looks like there is a memory leak. Kernel takes 1.83G at a startup but then grows.
Don Morris_1
Honored Contributor

Re: verification of glance system memory report

Narrowing it down to a particular DLKM may be tough depending on how the allocation was done.

kmeminfo should show which arenas are eating the memory... some arenas are more descriptive than others when it comes to knowing the clients (If it is all in M_TEMP it isn't easy to track down...).