hing like it.
That seems to be about STM (Software Transactional Memory). What you're
describing seems to be read lock-free using what I call PDR
(PCOW (Partial Copy On Write) Deferred Reclaimation). Examples of PDR
are RCU (used in Linux kernel), Maged Michael's SMR hazard pointers,
and
Ross Ridge wrote:
> Joe Seigh wrote:
>
>>Basically there's a race condition where an object containing the
>>refcount can be deleted between the time you load a pointer to
>>the object and the time you increment what used to be a refcount
>>and is possibly some
fender Problem), a form of PDR, and one using DCAS (compare and swap
of two separate locations) which only exists on MC68020 and MC68030
processors.
--
Joe Seigh
When you get lemons, you make lemonade.
When you get hardware, you make software.
--
http://mail.python.org/mailman/listinfo/python-list
safe if their internal
refcounting is synchronized properly. But note that in both cases,
the implemention is transparent to the user.
So as you say, a lot depends on how you access or want to access shared
structure members, e.g. with or without locking.
--
Joe Seigh
When you get lemons, you make lemonade.
When you get hardware, you make software.
--
http://mail.python.org/mailman/listinfo/python-list
