[openib-general] [ANNOUNCE] NetPIPE 3.7 release candidate 1

[Troy Benjegerdes]

Pradipta Kumar Banerjee wrote:
> Sean Hefty wrote:
>> Troy Benjegerdes wrote:
>>> Is the connection manager api considered 'stable' yet? Last I knew 
>>> it was still undergoing a lot of development.
>>
>> The connection manager API is relatively stable, and has been for a 
>> while. Changes to the API have come in the form of new options and 
>> calls, rather than changes to the existing calls.
> True. We have been using it for quite some time for all our work on 
> iWarp.
>
>>
>>> Wouldn't it be possible to adapt the existing tcp connection setup 
>>> code to work for Iwarp without using the connection manager? Most of 
>>> the time when I test IB networks, I just bind to ethernet eth0 
>>> interfaces anyway.
>>
>> My understanding is that it's not possible to connect iWarp QPs 
>> without using the connection manager.  For IB, it's possible to 
>> connect over sockets and exchange QP information over a TCP 
>> connection, but the same is not true for iWarp.
>>
>> - Sean
> Troy, the NetPIPE code needs to use the cm for successful working with 
> iwarp. May be the changes can be in a seperate file altogether (like 
> cm.c as in ibv.c) and have a seperate option in the Makefile to enable 
> the same.
>
>
in the future, I'd kinda like to deprecate the old out of bad IP QP 
connection setup, but it would be nice to separate the code into 
something like 'ib-cm.c'.

I would be happy to take a patch to use the CM instead of the IP 
connection setup we do now. I'm also interested in how to use the CM for 
things like the OpenFabrics verbs port of PVFS we are working on (which 
works on IB right now)