This is the whole purpose of the protocol. It is OS independent and ensures interoperability. Nobody will change their OS protocol implementation so it can communicate to Linux (or any other OS or vendor) that invented its own protocol... It is not OS (linux no exception) job to invent protocols.
But I think this argument have been bitten enough already. Arkady Arkady Kanevsky email: [EMAIL PROTECTED] Network Appliance phone: 781-768-5395 375 Totten Pond Rd. Fax: 781-895-1195 Waltham, MA 02451-2010 central phone: 781-768-5300 > -----Original Message----- > From: Woodruff, Robert J [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 26, 2005 11:33 AM > To: Kanevsky, Arkady; Sean Hefty > Cc: [EMAIL PROTECTED]; [email protected] > Subject: RE: [openib-general] round 2 - proposal for > socketbased connectionmodel > > > Arkady wrote, > >This is what we are trying to avoid. > >ULP should not change regardless whether or not it is running on IB, > >iWARP, VIA or any other RDMA transport. > > The whole point of the CMA is that the ULP can code to an > API that is independent of RDMA interconnect. The > CMA wire protocol can be documented to allow > non-Linux hosts to connect to a Linux box using > the same protocol. There is no need to change the existing > IB CM protocol to accomplish this. All that is needed is > to document that CMA protocol (contained in the private data > field of the IB CM requests). > > woody > > > _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
