rsocket Issue #2

Hefty, Sean sean.hefty at intel.com
Mon Feb 25 22:25:19 UTC 2019


Intel has contributors to the RDMA subsystem.  Lucy is the only person I know currently working on rsockets code specifically.  I will check her group and our Ethernet group to see if I can locate someone to assist her since she's out.

- Sean


> -----Original Message-----
> From: Chris Hegarty [mailto:chris.hegarty at oracle.com]
> Sent: Monday, February 25, 2019 2:20 PM
> To: Hefty, Sean <sean.hefty at intel.com>
> Cc: Lu, Yingqi <yingqi.lu at intel.com>; nio-dev at openjdk.java.net; Viswanathan,
> Sandhya <sandhya.viswanathan at intel.com>; Kaczmarek, Eric
> <eric.kaczmarek at intel.com>; Aundhe, Shirish <shirish.aundhe at intel.com>
> Subject: Re: rsocket Issue #2
> 
> Forgive me, but how do issues like the ones that we’ve encountered get fixed?
> Intel have contributors in this area, right?
> 
> -Chris
> 
> On 25 Feb 2019, at 19:51, Hefty, Sean <sean.hefty at intel.com> wrote:
> 
> >>>>> The `rpoll` behaviour I observe is clearly different than regular
> >>>>> `poll` ( which will wake up all waiters ). Is this a bug, or expected
> >>>>> behaviour of the thread-less rsocket implementation?
> >>>>
> >>>> This is likely an implementation issue, but the intent should be to mimic
> >> poll behavior here.  So I would consider this a bug, and it would take some
> >> work to figure out how to handle this in a way that doesn't result in
> races.
> >>>
> >>> Sure. Is it possible to get this issue into the librdma bug tracking
> system,
> >> and have it evaluated.
> >>
> >> Has this issue been filed in the librdma bug tracking system?
> >
> > There isn't a bug tracking system for any rdma-core components, which
> librdmacm is one of.  All bugs are just to be reported via an email to the
> linux-rdma kernel mailing list.
> >
> > I know Lucy submitted 1 or 2 issues to that mailing list, but I don't
> believe she ever received a response to any of them.  I can submit an email to
> that mailing list, but I would not anticipate any response to it.
> >
> > - Sean



More information about the nio-dev mailing list