adding rsockets support into JDK

Lu, Yingqi yingqi.lu at intel.com
Fri Nov 30 17:49:05 UTC 2018


Hi Chris,

We really appreciate all the help you and other OpenJDK networking engineers provide on this work, especially with the situation that this feature has software dependencies and special hardware needs for testing.

Let's work together to make the code in good shape for integration. Even though we cannot make it part of 12, we can trunk it and make it ready for 13 ahead of time :-)

Thank you!
Lucy 

>-----Original Message-----
>From: Chris Hegarty [mailto:chris.hegarty at oracle.com]
>Sent: Friday, November 30, 2018 9:38 AM
>To: Lu, Yingqi <yingqi.lu at intel.com>
>Cc: Alan Bateman <Alan.Bateman at oracle.com>; Viswanathan, Sandhya
><sandhya.viswanathan at intel.com>; nio-dev at openjdk.java.net; Aundhe,
>Shirish <shirish.aundhe at intel.com>; Kaczmarek, Eric
><eric.kaczmarek at intel.com>
>Subject: Re: adding rsockets support into JDK
>
>Lucy,
>
>> On 30 Nov 2018, at 17:19, Lu, Yingqi <yingqi.lu at intel.com> wrote:
>>
>> Hi Chris,
>>
>> Thanks very much for the help!
>>
>> I fully understand that the timeline for JDK12 is very tight. Given there are
>still two weeks till Dec.13th deadline for code integration, I would like still give
>it a try and see how far we can make. If yes, great. If not, we can trunk the
>code as soon as it is ready. Then JDK13 will be the target :-) For CSR, we can
>set the target to 13 for now.
>>
>> Does this sound reasonable?
>
>While this work is making very good progress, I just don't see how it can be
>ready to push before JDK 12 RDP 1. I and others are prioritising the code
>review and sending feedback, and I have more comments forthcoming.
>Testing to date has been challenging for us, but we are making some progress
>on that front.
>
>The CSR Fix Version should indicate the release in which the change is
>expected to be pushed. There can be some latency moving through the
>various stages when such a project nears completion. At this point I would be
>more comfortable to target 13.
>
>-Chris


More information about the nio-dev mailing list