HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MPAS Attribute 2
Operating System - HP-UX
1829260
Members
2005
Online
109988
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-13-2006 03:08 AM
01-13-2006 03:08 AM
In relation with the previous message "MPAS Attributes" with 32bit executable compiled on PA-RISC, I have recived an answer about the possibility to use MPAS process attribute only for ITANIUM.
Do someone know if exists a similar walkaround on PA-RISC (without recompile the code)? It's stange the availability of that facility for ITANIUM and not for PA-RISC. There is a planned patch related to this argument for PA-RISC?
Thanks
GM200
Do someone know if exists a similar walkaround on PA-RISC (without recompile the code)? It's stange the availability of that facility for ITANIUM and not for PA-RISC. There is a planned patch related to this argument for PA-RISC?
Thanks
GM200
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2006 04:16 AM
01-13-2006 04:16 AM
Solution
Sorry, guess I wasn't clear enough in the other thread.
There is no workaround on PA-RISC. The problem is not a software problem per se -- the fundamental chip architecture is different [I really don't want to go into gory details, and for that matter I'm not sure exactly what I can say in a public forum so I'm going to err on the side of caution and say no more], MPAS doesn't have the underlying functionality it needs to work on PA.
If you need more shared address space for a PA RISC binary you're going to have to recompile to 64-bit. The only other thing you can do is put all of your processes which share objects into the same Memory Window, and manage your objects yourself very carefully so that you only have <=2.75Gb of shared address space consumption at any given moment [you'll have to handle object creation/attach failure for the times that you exceed the address space]. I would think that 64-bit recompilation would be a lot simpler than that.
There is no workaround on PA-RISC. The problem is not a software problem per se -- the fundamental chip architecture is different [I really don't want to go into gory details, and for that matter I'm not sure exactly what I can say in a public forum so I'm going to err on the side of caution and say no more], MPAS doesn't have the underlying functionality it needs to work on PA.
If you need more shared address space for a PA RISC binary you're going to have to recompile to 64-bit. The only other thing you can do is put all of your processes which share objects into the same Memory Window, and manage your objects yourself very carefully so that you only have <=2.75Gb of shared address space consumption at any given moment [you'll have to handle object creation/attach failure for the times that you exceed the address space]. I would think that 64-bit recompilation would be a lot simpler than that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2006 05:18 AM
01-13-2006 05:18 AM
Re: MPAS Attribute 2
As the other thread is still open, please respond in THAT thread rather than open another thread on the same subject
http://forums1.itrc.hp.com/service/forums/questionanswer
.do?threadId=991499
http://forums1.itrc.hp.com/service/forums/questionanswer
.do?threadId=991499
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2006 11:52 PM
01-15-2006 11:52 PM
Re: MPAS Attribute 2
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