Path: utzoo!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!spool.mu.edu!uunet!microsoft!edwardj From: edwardj@microsoft.UUCP (Edward JUNG) Newsgroups: comp.sys.next Subject: Re: NeXT equivalent of Shared Memory and Semaphores on SysV Keywords: Shared Memory Message-ID: <71219@microsoft.UUCP> Date: 12 Mar 91 13:23:29 GMT References: <1991Feb21.152540.10679@noose.ecn.purdue.edu> <1991Feb22.044136.2498@rfengr.com> <1125@tokio.cs.utexas.edu> Reply-To: edwardj@microsoft.UUCP (Edward JUNG) Distribution: usa Organization: Microsoft Corp., Redmond WA Lines: 18 In article michael@hapuna.cs.ucla.edu (michael gersten) writes: > >My understanding of Mach (not necessarily NeXT OS) was that an external pager >could be written (and was written at CMU) to allow two unrelated tasks to >share memory. If this program would work on the NeXT, you should be able to >grab it, port an interface to look identical to the system 5 code, and presto!. Last I checked, the external pager interface was not enabled in the NeXT version of Mach (largely for performance reasons, I expect). I have not checked for this in the 2.0 release. Perhaps Morris Meyer could update the newsgroup? -- Edward Jung Microsoft Corp. My opinions do not reflect any policy of my employer.