What is the proper way to control the SLID used for outgoing umad sends? For example, when using LMC>0, the PathRecord returned from the SM for talking to a given remove node may have a SLID which is not the BaseLid for the sender. How does the sender ensure the correct SLID is used for the outgoing mad?
In reviewing the API it seems like the only way to do this is: void *umad = umad_alloc(...); // call various umad calls to initialize address and contents umad_get_mad_addr(umad)->path_bits = lower LMC bits of SLID; umad_send(..., umad, ...); Was path_bits an intentional omission in the API? It would seem that a function which could update the ib_mad_addr in a umad given a path record would seem appropriate. Todd Rimmer Chief Architect QLogic Network Systems Group Voice: 610-233-4852 Fax: 610-233-4777 [email protected] www.QLogic.com _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
