[ofa-general] [RFP] support for iWARP requirement - active connect side MUST send first FPDU

[Sean Hefty]

> I said "clean way to do it". ;-)

I'm referring to an rdma cm connection protocol for iWarp.  We have one 
for IB.  I mentioned uDAPL as a possibility because it abstracts the 
transport, QP, CQ, etc. anyway, and one could argue that the uDAPL iWarp 
provider should take necessary steps to support the uDAPL API.

I don't know that there's a need to change the iWarp architecture.

> Yes, this is the only "under the covers" solution I know of that will 
> work with existing HW.   However, I don't think it can be done totally 
> within the rdmacm or iwcm.  I think it involves providers "poll" 
> function to deal with the send completion/error and the passive side 
> recv completion/error.

This does present more of an issue for an rdma cm solution.  IB defines 
a communication established event that might be of use to pass 
information between the provider and the rdma cm.   But the provider 
would need to participate in the connection protocol.

- Sean