Hi,
BufferedInputStream is loaded early, and uses
AtomicReferenceFieldUpdater to provide
CAS functionality to allow for closing streams asynchronously. Using
Unsafe directly instead
does the exact same thing in the end, but avoids loading a few (4)
classes and thus brings
us a small startup
> On Apr 2, 2016, at 2:53 AM, Alan Bateman wrote:
>
>
> (cc'ing serviceability-dev as this is where this code is maintained).
>
>
>> On 02/04/2016 00:32, Mandy Chung wrote:
>> Hi Chris,
>>
>> Would jdk.internal.vm be appropriate for this VMSupoprt class?
> I agree.
Hello!
Please review the following enhancement:
https://bugs.openjdk.java.net/browse/JDK-8153332
http://cr.openjdk.java.net/~tvaleev/webrev/8153332/r1/
It was earlier discussed here:
http://mail.openjdk.java.net/pipermail/core-libs-dev/2016-March/039308.html
The motivation and algorithm are
Hi Roger,
Thanks for looking at the patch.
On 04/02/2016 01:31 AM, Roger Riggs wrote:
Hi Peter,
I overlooked the introduction of another nested class (Task) to handle
the cleanup.
But there are too many changes to see which ones solve a single problem.
Sorry to make more work, but I think
Hi All,
It was a mistake from my end. Please ignore it.
Thanks,
Abhijit
From: Abhijit Roy
Sent: Friday, April 01, 2016 02:35 PM
To: core-libs-dev@openjdk.java.net
Subject: https://bugs.openjdk.java.net/browse/JI-9032379
Hi,
Need some suggestion for this issue (2nd part).
(cc'ing serviceability-dev as this is where this code is maintained).
On 02/04/2016 00:32, Mandy Chung wrote:
Hi Chris,
Would jdk.internal.vm be appropriate for this VMSupoprt class?
I agree.
VMSupport::getAgentProperties simply calls JVM_InitAgentProperties.
java.management could call