David Schlosnagle wrote:
Rich and Jochen,
Part of your needs might be met by Doug Lea's proposed Fences API [1]
[2] for JDK7 by allowing an explicit volatile write (with the
appropriate memory barriers), without incurring the overhead of a
volatile read on each access. This fence could be used when a new
method/function is registered, while all the lookups would be regular
reference field accesses. The recent discussion of Fences and impacts
to the Atomic* classes [3] might also be of interest as well since
potential updates to the atomic field updaters could help build the
functionality you desire.
[1]:
http://cs.oswego.edu/pipermail/concurrency-interest/2009-January/005743.html
[2]:
http://g.oswego.edu/dl/jsr166/dist/docs/java/util/concurrent/atomic/Fences.html
[3]: http://cs.oswego.edu/pipermail/concurrency-interest/2010-April/006990.html
Those Fences sure look interesting to me. An explicit volatile write is
what I was looking for, so of course I am now excited to hear that
something like this is underway.
bye Jochen
--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/
--
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jvm-languages?hl=en.
