Article View: comp.sys.hp.hpux
Article #74Re: How is shared memory address range determined
From: Ken Green
Date: Sat, 23 Apr 1994 13:05
Date: Sat, 23 Apr 1994 13:05
24 lines
2121 bytes
2121 bytes
Patrick Coghlan (coghlan@bcarh5f8.bnr.ca) wrote: > I notice that under HP-UX, processes that attach a region of shared > memory end up with it at the same virtual address. > How does UNIX manage to do this? Does it preallocate virtual address > space for (max # of shared regions) regions of size (maximum region size)? > Then, use the key provided by the user to map him into a specific range > of virtual addresses (i.e. all users with the same key map into the same > address range)? No, HP-PA uses a 48bit or 64bit global virtual address map. A process is given 4 one GB quadrant from that, one is used for text, that is shared amgost all processes running the same program. The second of these quadrants is private data, the third is for shared libraries and the 4th is for shared memory. Both quadrants 3 and 4 are shared by all processes on the system. As the to process that are shareing a peice of shared memory are actualy sharing the same part of the global address map at this point, they have no choice but to see the shared memory segment at the same address. -- __________________email Ken.Green@kgcc.demon.co.uk _____________________ Ken Green Computer Consultancy Bodega, Jasmine Cres. Princes Risborough, Bucks. HP27 0AB, U.K.
Technical Details
Message-ID:
<Copr15.14z@kgcc.demon.co.uk>Path:
arc1-ca.pugleaf.net!gmd.de!nntp.gmd.de!Germany.EU.net!EU.net!howland.reston.ans.net!pipex!demon!kenReferences:
<1994Apr22.163441.19924@bcarh54a.bnr.ca>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fc89c,89dc02a43cbd3d6f X-Google-Attributes: gidfc89c,public X-Google-Thread: fcda7,89dc02a43cbd3d6f X-Google-Attributes: gidfcda7,public X-Google-Thread: 14b500,89dc02a43cbd3d6f X-Google-Attributes: gid14b500,public X-Google-ArrivalTime: 1994-04-25 09:39:57 PST Newsgroups: comp.sys.hp.hpux,comp.unix.programmer,bnr.unix Path: arc1-ca.pugleaf.net!gmd.de!nntp.gmd.de!Germany.EU.net!EU.net!howland.reston.ans.net!pipex!demon!ken From: ken@kgcc.demon.co.uk (Ken Green) Subject: Re: How is shared memory address range determined Message-ID: <Copr15.14z@kgcc.demon.co.uk> Date: Sat, 23 Apr 1994 13:05:29 GMT References: <1994Apr22.163441.19924@bcarh54a.bnr.ca> Organization: Ken Green X-Newsreader: TIN [version 1.2 PL2] Followup-To: comp.sys.hp.hpux,comp.unix.programmer,bnr.unix Lines: 24