[concurrency-interest] DirectByteBuffers and reachabilityFence

Paul Sandoz paul.sandoz at oracle.com
Tue Dec 15 16:05:21 EST 2015

> On 15 Dec 2015, at 14:54, Andrew Haley <aph at redhat.com> wrote:
> On 12/15/2015 12:37 PM, Vitaly Davidovich wrote:
>> To be fair, no empirical evidence has been presented; there is speculation
>> of scenarios it may hurt but nothing concrete.
> Exactly.  That was the answer!
>> I also think the bigger obstacle to changing this behavior is getting all
>> the different JVM implementations modified and not really the performance
>> impact.
> Yes, it's political as well.  reachabilityFence() is a great start.

The current API and implementation (with known limitations) is now in hs-comp:

  http://hg.openjdk.java.net/jdk9/hs-comp/jdk/rev/827ce3d74163 <http://hg.openjdk.java.net/jdk9/hs-comp/jdk/rev/827ce3d74163>

It will eventually wind it’s way into a JDK EA build but i don’t know exactly when.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20151215/7c71cee0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20151215/7c71cee0/attachment.bin>

More information about the Concurrency-interest mailing list