[ofa-general] peer to peer connections support

[Kanevsky, Arkady]

I think we need at least timeout parameter for accept.
One way to handle it is to include it into rdma_conn_param.
That way it can be used for both sides and not change to function
signatures.
But you would still need to recompile.

Thanks,

Arkady Kanevsky                       email: arkady at netapp.com
Network Appliance Inc.               phone: 781-768-5395
1601 Trapelo Rd. - Suite 16.        Fax: 781-895-1195
Waltham, MA 02451                   central phone: 781-768-5300
 

> -----Original Message-----
> From: Or Gerlitz [mailto:ogerlitz at voltaire.com] 
> Sent: Tuesday, December 18, 2007 5:37 AM
> To: Sean Hefty; OpenFabrics General; Jeff Squyres (jsquyres); 
> Jon Mason
> Subject: [ofa-general] peer to peer connections support
> 
> Hi Sean,
> 
> I wonder what will it take to implement peer to peer 
> connection establishment support in the IB CM (and RDMA-CM, 
> ofcourse). Also do you expect any API changes needed in order 
> to support that?
> 
> Reading through section 12.10.4, I was not sure to fully 
> understand the
> following: "The ServiceID implicitly defines whether the 
> service is client/server or peer to peer, but the application 
> must inform the CM so that the CM will handle the inbound REQ 
> correctly."
> 
> Such support would be useful in symmetric schemes such as 
> MPIs that open connections on demand and more applications 
> where each party can both accept and initiate connections. 
> For example, I understand that some work is done now at the 
> open mpi community to use the rdma-cm as a possible channel 
> for connection establishment.
> 
> Or.
> 
> _______________________________________________
> general mailing list
> general at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
> 
> To unsubscribe, please visit 
> http://openib.org/mailman/listinfo/openib-general
>