[swg] Re: [openib-general] TCP/IP connection service over IB

[Tom Tucker]

Ted:

I think it's relevant, so let's make sure my assumptions are correct:

- The ITAPI will be a "ULP" on OpenIB
- The ITAPI will create the IRD/ORD headers in its private data and
submit this as part of its connection establishment. 
- The ITAPI consumer at the remote peer will use this data to configure
it's local QP before accepting the connection

Over IB, the IRD/ORD private data will be prepended with a "private data
header" that contains the source and destination IP addresses, source
port, etc... The remote peer will not see this data as part of the
private data, but rather will see it in the CMA event in the upcall.

Over iWARP/MPA, there will be nothing else in the private data except
what was provided by the consumer (ITAPI in this case). The reason being
that this extra information (IP addressing info) is in the protocol
header proper.


On Mon, 2005-10-24 at 17:17 -0700, Ted H. Kim wrote:
> Just a comment on this one point ...
> 
> Sean Hefty wrote:
> >> I'm thinking that for iWARP, there won't be anything in the Private Data
> >> at all except consumer private data. Is that your expectation?
> > 
> > 
> > I believe so.  This is only trying to define a TCP/IP connection service 
> > over IB.  I'm assuming that there's no need to define something similar 
> > for iWarp.
> 
> Not sure if this is relevant for your intended base, but ITAPI 2.0
> for iWARP has a 16-byte IOH (IRD/ORD header)
> in MPA "private data" to note RDMA initiator/responder limits
> like the corresponding fields in the IB CM protocol.
> 
> -ted
>