home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!netsys!news!lsi!mhost!cl301!ameesh
- From: ameesh@lsil.com (Ameesh Desai)
- Newsgroups: comp.lang.c++
- Subject: C++ and Shared Memory (Was: Linked Lists in Shared Memory: )
- Message-ID: <1992Nov11.202728.7564@lsil.com>
- Date: 11 Nov 92 20:27:28 GMT
- References: <1992Nov10.114435.22735@ermes.enea.se>
- Sender: news@lsil.com (news caster)
- Reply-To: ameesh@lsil.com
- Organization: LSI Logic Corporation
- Lines: 35
- Nntp-Posting-Host: cl301
-
- In article 22735@ermes.enea.se, eny@ermes.enea.se (Erik Nykvist) writes:
- >> >=========
-
- [stuff deleted]
-
- >The proposed technique uses the new-operator with placement-syntax to
- >fix the vtbl-pointer in the object.
- >I have not thought about this very much. I have written ONE example
- >program that uses this.
- >My idea is that if you know the address of the object in shared memory
- >you could access it after having fixed the vtbl-pointer.
- >If you fork your process it is NOT necessary to fix the vtbl-pointer
- >because the forked process has the vtbl at the same address as the
- >parent process.
- >
- >Erik Nyquist
- >
-
-
- I guess if all processes that were to access the shared mem were to have the
- same parent (forked from one single process), what you say is true. However,
- in a more general case, you would like to provide access to the shared
- memory to processes that do not share the same parent.
-
- It is not clear to me if there is a "clean" way to share the pages simultaneously
- accross such processes. (when the pages contain C++ objects with vtbl ptrs).
-
- Ameesh
-
- ---
- ______________________________ o__
- | _ /| Ameesh Desai \ ,>/_
- | \`O.o' LSI Logic Corp. \__(_)`(_)_ email: ameesh@lsil.com
- | =(_|_)= MS E192, 1501 McCarthy Blvd. \ fax : (408) 433-6802
- |____U_______Milpitas, CA 95035____________\____________voice: (408) 433-4097
-