> From: Hal Rosenstock [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 07, 2005 2:36 PM > > On Thu, 2005-07-07 at 17:26, Fab Tillier wrote: > > > So it appears there are 3 choices: > > > 1. Port OpenIB Linux libraries to Windows and OpenIB Linux "diags" port > > > as well (second part is less work than next alternative) > > > 2. Port OpenIB Linux diagnostics to OSM vendor layer > > > 3. No OpenIB "Linux" diagnostics in the windows environment > > > > What about: > > 4. Port OpenIB Linux "diags" to Windows/IBAL. > > > > Seems like a pretty obvious choice, and what I've been talking about in my > > previous emails. > > Yes, that is another alternative but is similar to choice 2 in terms of > affecting all the applications.
All the applications will be affected by being ported from Linux to Windows, not to mention changes in the umad interface necessary to make it work on Windows. It has the benefits that the tools interface to the lowest API available to them. If interfacing at the lowest layer isn't important, the choice is between porting the diags to OSMV or porting umad to Windows. I don't know which is easier, and it probably doesn't matter. What matters is which gets done first. However, it doesn't sound that an effort from Eitan to port the diagnostics to OSMV would be accepted into the Linux SVN repository simply on the basis that it isn't umad. What gives? - Fab _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
