Operating System - HP-UX
1761318 Members
3138 Online
108901 Solutions
New Discussion

What is M_TEMP and why it consumes so much memory?

 
SOLVED
Go to solution
Don Morris_1
Honored Contributor

Re: What is M_TEMP and why it consumes so much memory?

pfdat - physical frame descriptors. This is the main metadata (per physical page) for physical memory.

htbl2_0 - That's the page table (virtual to physical translations... i.e. where you go to figure out what to load when you take a TLB miss fault)

pfn_to_virt - Physical to virtual reverse lookup table. (The anti-htbl2_0).

These are core VM metadata tables. You can't shrink them -- and you certainly need them to be there. These are *always* going to take a certain percentage (exact percentage can vary by release and patch level) of memory because they scale directly with the number of physical pages.

Don
wm_shi
Occasional Advisor

Re: What is M_TEMP and why it consumes so much memory?

Thank you Senthil and Kent,

I have studied your suggestion About why M_IOSYS consumes so much memory.
And we found the most recent patch is:
PHKL_29039 --> PHKL_32090
PHKL_30044
PHKL_29468 --> PHKL_31227
And in our system:
$/usr/sbin/swlist -l product | grep -E 'PHKL_29039|PHKL_32090|PHKL_30044|PHKL_29468 |PHKL_31227'
PHKL_30044 1.0 Memory leak fix for Core Bus ioscan
PHKL_31227 1.0 PCI patch,boot-time HPMC,PCI-X,OLA/R,AGP
PHKL_32090 1.0 SCSI IO Cumulative Patch

The above shows that we have no memory leak problem in our system.

So is there any further reason for that 1G memory?

Thanks,
William