[Openib-windows] RE: IBDM and IBMgtSim Proposal Comments

[Eitan Zahavi]

The point is that it is better to write user level code that is not
"performance critical" in a way that is not tailored to the actual
driver/Access layer. I think OpenSM vendor layer was proven to be adequate
for this purpose. 

It should be much simpler to port the existing tools on top of the
osm_vendor_api.h rather then porting them to IBAL api. 

EZ

Eitan Zahavi
Design Technology Director
Mellanox Technologies LTD
Tel:+972-4-9097208
Fax:+972-4-9593245
P.O. Box 586 Yokneam 20692 ISRAEL


> -----Original Message-----
> From: Hal Rosenstock [mailto:halr at voltaire.com]
> Sent: Thursday, July 07, 2005 10:45 PM
> To: Eitan Zahavi
> Cc: openib-general at openib.org; openib-windows at openib.org
> Subject: RE: IBDM and IBMgtSim Proposal Comments
> 
> Hi Eitan,
> 
> On Thu, 2005-07-07 at 14:58, Eitan Zahavi wrote:
> [snip]
> 
> > > In the OpenIB architecture, umad is the lowest layer library and the
> > > diagnostics are built on that. The OSM vendor layer is built on top
> > of
> > > this. So when the umad and mad libraries are ported to Windows,
> > > everything on top of this will work. This includes all diagnostics
> > > (OpenIB ones as well as the additional tools you are proposing to
> > add).
> > [EZ] There is no need to port UMAD to windows!!! We already have OSM
> > Vendor ported to it. It works on top of the existing IBAL API
> > (actually this is the first OSM Vendor that was ever built).
> 
> There is if the OpenIB diagnostics and other applications in the Linux
> environment which are not on top of the "OSM" vendor layer are to work
> in the Windows environment. That was what started this whole thread.
> 
> [snip]
> 
> I'll comment on the rest separately.
> 
> -- Hal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20050707/3105323e/attachment.html>