home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.centerline.com!franl
- From: franl@centerline.com (Fran Litterio)
- Newsgroups: comp.sys.hp
- Subject: Re: mmap on HP-UX 9.0 on s700
- Date: 7 Nov 92 21:09:01
- Organization: CenterLine Software, Inc.
- Lines: 26
- Message-ID: <FRANL.92Nov7210901@draco.centerline.com>
- References: <FRANL.92Nov7110620@draco.centerline.com> <BxD92u.E80@fc.hp.com>
- NNTP-Posting-Host: 140.239.3.116
- In-reply-to: jsm@fc.hp.com's message of Sat, 7 Nov 1992 21:59:18 GMT
-
- jsm@fc.hp.com (John Marvin) writes:
-
- > Fran Litterio (franl@centerline.com) wrote:
- > : If this is so, then how is dld.sl guaranteed to be able to map the
- > : text/data of mylib.sl at the same VM address for all programs which
- > : were linked against it?
- >
- > It doesn't. The data is mapped into the second quadrant, which is private
- > (not shared with other processes). The text is mapped into the 3rd or 4th
- > quadrant, which is shared with all processes. But when it is mapped by
- > the first process that uses it, it can be placed anywhere within the 3rd
- > or 4th quadrant.
-
- Don't you mean "anywhere within the 3rd or 4th quadrant that isn't
- already allocated to a shared library that another process has
- mapped"?
-
- So if libfoo.sl's text pages are mapped for the very first time by any
- process, they will not be assigned virtual addresses that are used by
- libbar.sl's text pages in another process that was started a minute
- earlier? Even if the program that maps libfoo.sl does not map
- libbar.sl?
- --
- franl@centerline.com || Fran Litterio, CenterLine Software R&D
- 617-498-3255 || 10 Fawcett St, Cambridge, MA, USA 02138-1110
- "It's not the thing you fling, it's the fling itself." -- Chris Stevens
-