On Feb 7, 2013, at 3:06 PM, Dan Berindei <dan.berindei(a)gmail.com> wrote:
</snip>
3. Requires exclusive access, even for read operations. Our lock() implementation still
allows read operations.
What happens on other nodes? Do we have to block threads on other nodes that want to read
the entry from their own L1 cache?
I think the intention of this requirement is not really to block readers from executing,
but from seeing incomplete values. So we should be complying with the spirit (if not the
letter) of the specification if we made a copy of the entry before handing it over to the
EntryProcessor.
^ That's a very good idea. I'm playing around with a solution based around this
which would simplify the solution for this.
Cheers,
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org