Xref: utzoo comp.unix.xenix.sco:382 comp.unix.internals:530
Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!att!mcdchg!ddsw1!proxima!olsa99!tabbs!pscnet!kean
From: kean@pscnet.UUCP (Kean Johnston)
Newsgroups: comp.unix.xenix.sco,comp.unix.internals
Subject: Shared Memory on SCO Xenix
Keywords: shmem Xenix
Message-ID: <1589@pscnet.UUCP>
Date: 3 Oct 90 17:31:31 GMT
Followup-To: comp.unix.xenix.sco
Organization: Progressive Systems College
Lines: 19

Please could someone clarify a point for me relating to shared memory under
SCO Xenix, specifically Xenix/386 release 2.3.2 or 2.3.3.
In his excelent book "Advanced Unix Programming" by Marc J. Rochkind,
in the chapter on IPC's and shared memory he states that under Xenix, after
having mapped a segment as shared, you have to unmap it before you can
issue any system calls. This means that you have to keep on mapping and
unmapping the shared data segment each time you need to make a system call.
Is this still true of Xenix, or is the book just outdated. It WAS written
6 years ago after all.
Also, is there any MAJOR speed advantage of using shared memory over
semaphores? Anyone really pushed semaphores to the limit out there ?
Any help at will would be greatly appreciated.
Thanks in advance,


-- 
 Kean Johnston: kean@pscnet.UUCP    Bang: ..!ddsw1!olsa99!tabbs!pscnet!kean
-----------------------------------------------------------------------------
                "I think; therefore I AM" - Rene Descartes