Operating System - HP-UX
1753902 Members
9349 Online
108810 Solutions
New Discussion юеВ

maximum limit for stack(kbytes)

 
Ranveer
Advisor

maximum limit for stack(kbytes)

Hi gurus

Please help me in updating the following ulimit -a output.
#ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 966852
stack(kbytes) 8192
memory(kbytes) unlimited
coredump(blocks) 4194303

i want to know the maximum values for the data & stack. is it possible to make them unlimited? I have little idea that the values are controlled from kernel paermeters
maxdsiz & maxdsiz_64bit. The valu is as follow.
maxdsiz 990056448 - 990056448
maxdsiz_64bit 4294967296 - 4294967296

Thanks in advance.

regds
Ranveer
I am an HPE employee

Accept or Kudo

5 REPLIES 5
Venkatesh BL
Honored Contributor

Re: maximum limit for stack(kbytes)

These values can be configured using sysconfig or dxkerneltuner. Check the manpage of "sys_attrs_proc" for more info.

Note that some of these settings require a reboot.
Michael Schulte zur Sur
Honored Contributor

Re: maximum limit for stack(kbytes)

Hi,

are we talking here about HP-UX?

greetings,

Michael
Ranveer
Advisor

Re: maximum limit for stack(kbytes)

extremely sorry for wrong posting.

yes my server is running HP UX 11.11 with dec 04 patches. L2000-44 with 4GB RAM

regds
ranveer
I am an HPE employee

Accept or Kudo

Jeff Schussele
Honored Contributor

Re: maximum limit for stack(kbytes)

Hi Ranveer,

The limits are set with:

data ==> maxdsiz (32-bit) & maxdsiz_64bit

stack ==> maxssiz (32-bit) & maxssiz_64bit

NOTE: Changes to either will require a reboot.

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
A. Clay Stephenson
Acclaimed Contributor

Re: maximum limit for stack(kbytes)

You do not want to make maxssiz unlimited; in fact, 64MB is extremely generous. Be aware that in 32-bit applications because stack and data are allocated from the same 1GB quadrant, the maxssiz reduces the amount of memory that is available for dynamic allocation. Somewhere in the 32-64MB range is a good value for massiz for all but very poorly written code. (I might make an exception for some FORTRAN).
If it ain't broke, I can fix that.