Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!samsung!sdd.hp.com!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!motcsd!mcdcup!mcdchg!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.i386
Subject: Re: Two Programming Questions
Keywords: Shared Memory Locking
Message-ID: <1990Aug28.221823.3897@chinet.chi.il.us>
Date: 28 Aug 90 22:18:23 GMT
References: <380@icjapan.uucp> <1990Aug27.230044.13699@virtech.uucp>
Organization: Chinet - Chicago Public Access UNIX
Lines: 14

In article <1990Aug27.230044.13699@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes:

>>just forget about using shared memory and use a real file with file
>>locking instead.  If it is being constantly accessed, it will be in
>>memory anyway.

I've considered opening a real file mapped against the shared memory
just to be able to use the file locking routines to arbitrate
access (i.e. lock the file region but access the memory segment
instead).  Does anyone know how this would work performance-wise
compared to any reasonable alternatives?

Les Mikesell
  les@chinet.chi.il.us