Operating System - HP-UX
1748201 Members
2921 Online
108759 Solutions
New Discussion юеВ

Re: memory management + swap + /usr/lib/dld.sl --not enough space

 
manu_5
Frequent Advisor

Re: memory management + swap + /usr/lib/dld.sl --not enough space

Thats the case for now ...but i want to know about the paging process priorities and which type it will take first.
manu_5
Frequent Advisor

Re: memory management + swap + /usr/lib/dld.sl --not enough space

maxdsiz 0XFFFFF000

this is my maxdisiz and physical ram is 8gb.
keith persons
Valued Contributor

Re: memory management + swap + /usr/lib/dld.sl --not enough space

Manu,

1) yes, you will need to reboot for the priority of swap to change as displayed by swapinfo. This is required because there is no real method to unmount the swap device while it is active. After reboot a new device swap table entry will generated and the new priority schema should be reflected in swapinfo output.

2) The simple answer is, when psuedo-swap is active, the swap algorithm as used by the kernel will 'allocate' from memory first to reduce/eliminate the need for any IO requests. It's easiest to think of psuedo-swap as essentially a counter, nothing more.

If memory consumption does actually require pages be physically paged or processes swapped, this will actually occur on the lowest priority swap device first and psuedo-swap previously 'allocated' to the page/process will be reduced by that approximate amount and the device swap usage will increase accordingly.

Hope this clears up any confusion.

Keith
Sridhar Bhaskarla
Honored Contributor

Re: memory management + swap + /usr/lib/dld.sl --not enough space

Hi Manu,

Did you get a chance to capture the error?. Often these errors could be misleading. Not enough space can also be associated with nfile or nproc/maxuprc kernel limitations. Look at your kernel parameters like nfile, maxuprc and nproc. sar -v can give you info on nfile and nproc. Look at the "ov" parameter. If it is greater than 0, then those parameters did overflew.

The subtle parameter is "maxuprc". This is per user basis. If some users get the errors and other s won't then this could be a culprit. Do a "ps -ef|grep user|grep -v grep|wc -l" and compare it with your maxuprc parameter. If it is close, then there is a good chance you will need to increase it.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Bill Hassell
Honored Contributor

Re: memory management + swap + /usr/lib/dld.sl --not enough space

Your maxdsiz of maxdsiz 0XFFFFF000 is too large. From SAM:

The value specified for tunable parameter "maxdsiz", "0XFFFFF000", evaluates to "4294963200" which is more than the maximum allowed value of "2063835136".

Now this is not a problem as such. 32bit programs by default cannot address more than 960 megs (or up to about 1750 megs with special compiler options). And with even more restricted options, a 32bit program might get access to a bit under 3Gb.

So you need to identify the program(s) that are getting the out-of-memory error message and see if the problems are due to 32bit limitations. Have your programmers take a look at the Memory Management and Process Management white papers from the HP website (docs.hp.com) to understand the extreme limitations of 32bit programs.


Bill Hassell, sysadmin