Return to BSD News archive
Xref: sserve comp.unix.programmer:11448 comp.unix.bsd:12519 Newsgroups: comp.unix.programmer,comp.unix.bsd Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!sol.ctr.columbia.edu!emory!news-feed-1.peachnet.edu!concert!uvaarpa!cv3.cv.nrao.edu!csugrad.cs.vt.edu!gwaldron From: gwaldron@csugrad.cs.vt.edu (Glenn Waldron) Subject: Re: mmap for shared memory, how to use efficiently? Message-ID: <1993Sep2.135345.4889@nrao.edu> Followup-To: comp.unix.programmer,comp.unix.bsd Sender: news@nrao.edu Organization: Virginia Tech Computer Science Dept, Blacksburg, VA X-Newsreader: TIN [version 1.1 PL9] References: <MUTS.93Sep1221625@compi.hobby.nl> Date: Thu, 2 Sep 1993 13:53:45 GMT Lines: 17 Another way to do shared memory is the stardard ipc functions in SVR4. See the following man pages: stdipc, shmget, shmctl, shmop I cannot comment on the speed of this facility relative to using a disk file. Oh, and you may need to protect your shared memory with semophores; in that case see: semget, semctl, semop - Glenn. Glenn A Waldron gwaldron@csugrad.cs.vt.edu CS Department - Virginia Tech gwaldron@mitre.org ---------------------------------------------------------------------------