Tom Tucker and I have talked about this, and agree that we could to create a set of agnostic services like ib_connect_qp(), ib_create_psp(), ib_accept_cr(), ib_reject_cr(), and the associated connection events similar to kdapl. These service would then use the AT service and core IB cm services for IB devices -and- plug into our up and coming iwarp-specific connection services for IWARP devices. Thus a common connection manager.
However, we need to get the iwarp specific connection services code up, reviewed by all, and running before continuing onto the higher level services. Once we post our iwarp-specific services to the iwarp branch, ya'll can chew on that and think about these higher level services. Thoughts? > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sean Hefty > Sent: Friday, August 19, 2005 2:44 PM > To: Talpey, Thomas > Cc: [EMAIL PROTECTED]; Christoph Hellwig; > [email protected] > Subject: Re: [openib-general] [ANNOUNCE] Initial trunk > checkin of ISERinitiator > > Talpey, Thomas wrote: > > By far the largest is the connection and addressing models. > > There is, as yet, no unified means for an upper layer to connect > > over any other transport in the OpenIB framework. In fact, there > > isn't even a way to use IP addressing on the OpenIB framework > > now, which is an even more fundamental issue. > > The address translation (AT) service in the trunk permits using IP > addresses to obtain connection information. > > - Sean > > _______________________________________________ > openib-general mailing list > [email protected] > http://openib.org/mailman/listinfo/openib-general > > To unsubscribe, please visit > http://openib.org/mailman/listinfo/openib-general > _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
