In the current implementation there is a field in the registry that contains either ib or eth for every port. As we move towards RoCE, I believe that a new keyword should be introduced: "roce". In the case of a Roce port, the mlx4_bus will create an hca device for which a winverbes driver will be registered.
It seems to me that for Ethernet only port the hca device should not get any notification (In other words the mlx4_bus driver should block that). I must say that I have a pre-mature version of roce working with performance tests and ND, that needed relatively small changes. I hope that it will not turn out that we have many bugs/races in the current code base. Thanks Tzachi > -----Original Message----- > From: Hefty, Sean [mailto:[email protected]] > Sent: Monday, December 13, 2010 8:05 AM > To: Fab Tillier; Uri Habusha; '[email protected]' > Cc: Galina Tcharny; Eitan Peretz; Gilad Margalit > Subject: RE: [ofw] [patch] [winverb] fix BS in WinVerbs when getting an > event for non IB port > > > That said, you bring up a good question: how is RoCE going to be > handled > > with this stack? Is it going to show up as another HCA? How will > WinVerbs > > work over RoCE ports? > > Winverbs should be modified to work with RoCE regardless of the final > implementation. Does windows support a filter driver registering for > multiple device classes? (I'd guess so, even if it required different > .inf files.) I'm not sure how many kernel changes will be needed, > versus modifications to the winverbs library. RoCE support will need > to be propagated up through libibverbs once the Linux APIs for that are > merged. > > RoCE will still need QP1 and IB CM support. > > - Sean _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
