[openib-general] OpenSM on mthca

[Tziporet Koren]

Hi,
The osm_vendor_mlx_ts_anafa.c is very close to what you need, it just
contain some hard-coded values (e.g. one port) that will not suite Tavor.
But you can easily take it and change it in the way that will eliminate the
need for any VAPI call in OpenSM.

Of course you need to close the API for user space but this should be done
in any case.

Tziporet

> -----Original Message-----
> From: Roland Dreier [mailto:roland at topspin.com]
> Sent: Saturday, August 07, 2004 3:03 AM
> To: Tom Duffy
> Cc: openib-general at openib.org
> Subject: Re: [openib-general] OpenSM on mthca
> 
> 
>     Tom> I have only just began to look into it.  What is it going to
>     Tom> take to do this port?  Is it possible with the current mthca
>     Tom> driver?
> 
> I think all the VAPI calls from osm_vendor_XXX.[ch] need to be
> removed.  It's not clear to me how close osm_vendor_mlx_ts_anafa.c is
> to what we would need.
> 
> It's definitely possible on top of the current mthca driver, since
> sending and receiving MADs is all that is required.
> 
> In any case all this MAD/GSI discussion is going to lead to a change
> in the userspace interface (not to mention the requirement of being
> 32/64 clean) so I wouldn't want to spend too much effort getting
> opensm working on the current tree.
> 
>  - Roland
> _______________________________________________
> openib-general mailing list
> openib-general at openib.org
> http://openib.org/mailman/listinfo/openib-general
> 
> To unsubscribe, please visit 
> http://openib.org/mailman/listinfo/openib-general
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20040810/291a42d7/attachment.html>