pregions memory

[jpcast_real]

Does anyone knows if there is any limitation in the maximun number of allowed preregions . I have some processes which are using a real big amount of memory and I discover an error when I use the tool procsize

Dartanan:/opt/software/hp-ux> ./procsize -p 14764
libp4 (6.93): Opening /stand/vmunix /dev/kmem

Loading symbols from /stand/vmunix
regions set to 1000
hpux 11.11 64 bit in Wide mode
nproc=2068
pid Comm UAREA TEXT DATA STACK SHMEM IO MMAP Total
14764 java v 1248 16 12271 528 0 0 176794 190857
Dartanan:/opt/software/hp-ux> ./procsize -p 11976
libp4 (6.93): Opening /stand/vmunix /dev/kmem

Loading symbols from /stand/vmunix
regions set to 1000
hpux 11.11 64 bit in Wide mode
nproc=2068
pid Comm UAREA TEXT DATA STACK SHMEM IO MMAP Total
procsize (error) pid 11976 has more than 1000 pregions. Unable to process.

[curt larson_1]

this might be helpful in answering your questions:
http://docs.hp.com/en/5965-4641/ch01s06.html

[MAUCCI_2]

hi,

i guess procsize may be a hp support tool only, and maybe a new version fixes this limitation?

-cyrille

[Ermin Borovac · Accepted solution]

Try running procsize with -P option.

-P # Override the pregion limit (default 1000)

[Emil Velez]

A pregion is a part of memory of a process. A process has the following pregions

text
data
mmap - for memory mapped files
they can be shared for shared libraries
or private for files opened in memory mapped mode
Shared Memory
Stack - for process stack
user area- this is for each thread in the proces.

The size of the text pregion is limited by the compilation type 32 vs 64 bit and the kernel paramter maxtsize or maxtsize64

The size of the data pregion is again limited by the kernel parameters maxdsize or maxdsize64

The maxssize limits the stack and the shmmax limits the size of a single piece of shared memory that can be created.

I hope this helps.

[jpcast_real]

And how can I know if the maxtsize , maxdsize and so on , has reached its limit....

Thanks

[MAUCCI_2]

Well,

monitor the process with glance and go to process memory regions details...

++Cyrille