[ntp:hackers] [Gpsd-dev] A lightweight synchronization mechanism for shared memory
f96hajo at chalmers.se
Fri Mar 25 09:36:58 UTC 2011
>> If the writer crashes in a mid-update, say entry 3, then until the next
>> alive writer has overwritten that entry, say when it just claims to be
>> writing next entry 4, the reader may get the idea that the previous
>> entry (number 3) is now good and usable.
> I did state up front that my approach is specifically designed for a
> single writer with one or more readers: If the writer crashes then you
> obviously get no more valid updates! :-)
Sure, but if another writer then comes online, is it possible for the
reader to be fooled to read and use some old inconsistent data?
More information about the hackers