| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
fixed shared memory segments
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 fixed shared memory segments - Oct. 6, '06, 9:00:56 AM
|
|
|
lforster
Posts: 11
Joined: Dec. 12, '05,
Status: offline
|
We are porting complex system software from UnixWare to SFU. The subject matter experts are long gone. We use two segments of shared memory where the base addresses are fixed. Although I can change the initial base addresses, they must remain fixed because there are many pointers within each segment that cannot be adjusted for each process that attaches to and uses that segment. My question is, what ranges of memory are available to use in this manner? I'm currently using 0x70000000 and 0x78400000. I suspect one or both of these may be bad choices because we have scenarios where all the korn shell processes are "blown away". Can you provide any guidance on picking valid fixed addresses for shared memory in the SFU environment?
|
|
|
|
|
RE: fixed shared memory segments - Oct. 6, '06, 10:07:36 AM
|
|
|
markfunk
Posts: 669
Joined: Mar. 31, '03,
Status: offline
|
you definitely want to stay away from anything above 0x70000000.
This is where all the shipped shared libraries are loaded by default.
As more libraries are shipped, they will continue to creep down
in the address space.
Probably 0x40000000 to 0x4fffffff is a good a place as any for now.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
