HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MPAS Attributes
Operating System - HP-UX
1829738
Members
1793
Online
109992
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
Forums
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
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
01-12-2006 10:47 PM
01-12-2006 10:47 PM
In relation with the previous message "Allocation Shared Memory Limit 2.75GB wolkaround" with 32bit executable compiled, I have read on an HP technical white paper ("Adaptative Address Space") the possibility to use all the "4GB, i.e. all the 4 quadrants," [...] "for the process to consume in any manner it chooses" by using the MPAS process attribute (chatr -as mpas). Do someone know if this option work only for ITANIUM or also on PA-RISC (64bit maschine S.O. 11.23)? Can someone provide some information about? Can I use this option in conjuntion with the memory window functionality?
Thanks
GM200
Thanks
GM200
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2006 10:58 PM
01-12-2006 10:58 PM
Re: MPAS Attributes
Hi,
You can check this thread at DSPP,
http://h21007.www2.hp.com/dspp/ml/showArchiveMessage/1,,4!04!01!0054,00.html
-Arun
You can check this thread at DSPP,
http://h21007.www2.hp.com/dspp/ml/showArchiveMessage/1,,4!04!01!0054,00.html
-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2006 12:43 AM
01-13-2006 12:43 AM
Solution
MPAS is Itanium only. PA-RISC doesn't support the aliasing features needed to make MPAS work.
Memory Windows can be used at the same time as MPAS from a system-viewpoint, but there's no meaning to having Memory Windows in an MPAS process -- it has the entire address space to work with (for 32-bit, 64-bit actually do include a section of the global shared address space as well... but 64-bit processes don't need memory windows (yet, anyway... when are you folks going to start consuming exabytes? :) ) so that's a moot point). Anything it needs to share gets mapped to a private alias within the MPAS process - doesn't matter how it gets shared to non-MPAS, really.
For 11.23 PA-RISC, if you need more than 2.75Gb of shared address space -- you must go 64-bit. Besides -- if you're hitting 3Gb now - you know you'll be hitting 4Gb soon enough, and nothing's going to save you in 32-bit land at that point.
Memory Windows can be used at the same time as MPAS from a system-viewpoint, but there's no meaning to having Memory Windows in an MPAS process -- it has the entire address space to work with (for 32-bit, 64-bit actually do include a section of the global shared address space as well... but 64-bit processes don't need memory windows (yet, anyway... when are you folks going to start consuming exabytes? :) ) so that's a moot point). Anything it needs to share gets mapped to a private alias within the MPAS process - doesn't matter how it gets shared to non-MPAS, really.
For 11.23 PA-RISC, if you need more than 2.75Gb of shared address space -- you must go 64-bit. Besides -- if you're hitting 3Gb now - you know you'll be hitting 4Gb soon enough, and nothing's going to save you in 32-bit land at that point.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2006 11:53 PM
01-15-2006 11:53 PM
Re: MPAS Attributes
I cannot solve the problem
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP