Roland Dreier wrote:


The opensm issues I saw were:
 - GUIDInfoRecord SA queries are not implemented (I think), so by
   default my code does a (non-compliant) SM class query to get ports'
   GUIDs.
Yes this is correct we never got requested for that query.
If you are only interested in obtaining the guid of the port you can
simply use NodeInfoRecord and you get the guid in the NodeInfo.
But you probably know that. Is there anything more you expect to get from
the GUIDInfo? Are you using/having multiple GUIDs for port?

 - opensm sometimes sends a PortInfoRecord with a lot of zeroed-out
   entries (eg I got 30+ entries in a reply that only covered 3 real
ports).
This must be an RMPP bug of some sort. How easy is it to reproduce?
Please give us some hints.
To save on looking at a lot of switch ports, my code does
   a query for PortInfoRecords with a component mask that selects by
   local port number and gets all the port 1s followed by all the port
   2s in the fabric.

 - R.



------------------------------------------------------------------------

_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to