Re: [PATCH RFC 0/2] IB device in-kernel API support indication

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 09, 2019 at 12:25:23AM +0000, Hefty, Sean wrote:
> > > > So, you can choose to hide all of this, but I wouldn't describe SRD as
> > > > unconnected, more as 'automatically connected'.
> > 
> > > Is there any difference from a user perspective?
> > 
> > Unconnected implies there is no state. Automatically connected
> > implies there is a state but it is hidden from the user.
> 
> Brian said that the state is maintained NIC to NIC, not at the QP
> level.  He went further and suggested that the state is maintained
> for some period of time, and isn't necessarily tied to the lifetime
> of the QP.  The SRD QPs are unconnected, but let's argue what the
> definition of a connection is now.

I didn't say QP, I said the protocol was 'automatically connected'

SRD seems similar to the IB spec concept of RD which is described as
an unconnected QP running a 'connection oriented' RD protocol.

EFA wants to hide the objects related to connection state (ie in IBA
RD terms RDC and EEC) of the protocol, thats fine, but lets not
pretend it doesn't exist, OK?

Sagi wanted to know where CM was done, and now we know. It is hidden
in the NIC, and managed automatically.

Jason



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux