- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Shared library mapping to memory
Operating System - HP-UX
1752749
Members
4853
Online
108789
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
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
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
тАО12-18-2002 07:16 AM
тАО12-18-2002 07:16 AM
Hi,
When I see my process's memory region by GlancePlus,
I find that all my shared libraries are mapped at MEMMAP/Priv area.
However, when I run utils provided by others, such as pxdb, the shared libraries they use are mapped as MEMMAP/Shared.
Would anyone tell me how to assing shared library's image to shared memory?
My environ info:
OS:HP-UX 11.0
Tnanks in advance, Takeshi Sato
Model:A500
When I see my process's memory region by GlancePlus,
I find that all my shared libraries are mapped at MEMMAP/Priv area.
However, when I run utils provided by others, such as pxdb, the shared libraries they use are mapped as MEMMAP/Shared.
Would anyone tell me how to assing shared library's image to shared memory?
My environ info:
OS:HP-UX 11.0
Tnanks in advance, Takeshi Sato
Model:A500
takeshi
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2002 07:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2002 08:16 AM
тАО12-18-2002 08:16 AM
Re: Shared library mapping to memory
Thank you Jean-Louis,
I followed your question and I got it. MEMMAP/Shared.
Please let me explain the reason I asked the question in first place.
I have two same processes running which links a lot of shlibs.
The first one takes a quite long time to start up, (to reach the main() ) which I expected. Maybe it is taking a lot of time to load the libraries.
The problem was that the second one takes about the same time to start up.
I had two assumptions here.
1) Before reaching main(),
all the shlibs are loaded from file system. ("deferred" are set but I understand that loading is done at the startup anyway)
2) Once a shared library is loaded, it will not be loaded again from filesystem. Even if another process which uses the same shared library is started. So the second process starts up quicker.
And the result after MEMMAP/Shared? The same.
The second process takes about the same time to startup.
Would Jean-Louis or anyone tell me why this is the case?
Or am I wrong whole together?
Maybe a task besides loading shared libraries is taking time?
Thanks again in advance.
Hope one day I will be in place to answer the questions.
Takeshi Sato
I followed your question and I got it. MEMMAP/Shared.
Please let me explain the reason I asked the question in first place.
I have two same processes running which links a lot of shlibs.
The first one takes a quite long time to start up, (to reach the main() ) which I expected. Maybe it is taking a lot of time to load the libraries.
The problem was that the second one takes about the same time to start up.
I had two assumptions here.
1) Before reaching main(),
all the shlibs are loaded from file system. ("deferred" are set but I understand that loading is done at the startup anyway)
2) Once a shared library is loaded, it will not be loaded again from filesystem. Even if another process which uses the same shared library is started. So the second process starts up quicker.
And the result after MEMMAP/Shared? The same.
The second process takes about the same time to startup.
Would Jean-Louis or anyone tell me why this is the case?
Or am I wrong whole together?
Maybe a task besides loading shared libraries is taking time?
Thanks again in advance.
Hope one day I will be in place to answer the questions.
Takeshi Sato
takeshi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2002 12:51 AM
тАО12-19-2002 12:51 AM
Re: Shared library mapping to memory
Hi,
I'm not really an expert in shared libs, but perhaps you could have a look at some commands and docs like :
- fastbind : improves Shared Library Start-Up Time ...
- chatr : so many options ...
- HP-UX Linker and Libraries User's Guide at http://www.docs.hp.com/hpux/onlinedocs/B2355-90654/B2355-90654.html
Regards.
I'm not really an expert in shared libs, but perhaps you could have a look at some commands and docs like :
- fastbind : improves Shared Library Start-Up Time ...
- chatr : so many options ...
- HP-UX Linker and Libraries User's Guide at http://www.docs.hp.com/hpux/onlinedocs/B2355-90654/B2355-90654.html
Regards.
It works for me (┬й Bill McNAMARA ...)
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