Draft JEP: Socket API for Remote Direct Memory Access (RDMA)
yumin.qi at gmail.com
Wed May 1 02:26:22 UTC 2019
Have you integrated RDMA implementation into jdk13? I haven't seen
messages related to this JEP since the last email in this thread.
On Mon, May 21, 2018 at 8:37 AM Lu, Yingqi <yingqi.lu at intel.com> wrote:
> Hi Chris,
> Thank you for the feedback.
> Yes, on the platform that does not support rsocket, UOE is thrown. I will
> make it clear in the document.
> I will modify the reference links too.
> >-----Original Message-----
> >From: Chris Hegarty [mailto:chris.hegarty at oracle.com]
> >Sent: Monday, May 21, 2018 3:42 AM
> >To: Lu, Yingqi <yingqi.lu at intel.com>; jdk-dev at openjdk.java.net
> >Cc: Viswanathan, Sandhya <sandhya.viswanathan at intel.com>; Aundhe,
> >Shirish <shirish.aundhe at intel.com>; nio-dev at openjdk.java.net; Kaczmarek,
> >Eric <eric.kaczmarek at intel.com>
> >Subject: Re: Draft JEP: Socket API for Remote Direct Memory Access (RDMA)
> >Hi Lucy,
> >On 18/05/18 19:21, Lu, Yingqi wrote:
> >> Hi All,
> >> We just submitted a JEP draft
> >> https://bugs.openjdk.java.net/browse/JDK-8203434. The proposal is to
> >> enhance the Java Socket API to support Remote Direct Memory Access
> >> (RDMA) using the rsocket protocol on the Linux-based platforms.
> >This latest version looks very good. Just a few minor minor comments that
> >did not noticed before.
> >1) What is the behavior on platforms that do not support RDMA?
> > For example, will jdk.net.Sockets::openRdmaSocketChannel
> > throw UnsupportedOperationException? If so, then maybe make
> > that clear in the API sketch in the description.
> >2) Links to external references seem to have been inadvertently
> > dropped. Prefer markdown links, e.g.
> > ... form [Wikipedia][wikirdma] ...
> > [wikirdma]:
More information about the jdk-dev