- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- What is M_TEMP and why it consumes so much memory?
Operating System - HP-UX
1761318
Members
3138
Online
108901
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2006 01:36 AM
03-13-2006 01:36 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2006 02:39 PM
03-14-2006 02:39 PM
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
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
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP