On 4/17/2017 4:56 PM, Dasaratharaman Chandramouli wrote: > When the bit 26 of capmask2 field in OPA classport info > query is set, SA will query for OPA path records instead > of querying for IB path records. If/when additional SA query types are supported for OPA, will each additional SA query type have separate CapMask2 bit or will they be combined into 1 ? For example, would SA MCMemberRecord be different for OPA (perhaps 32 bit MLID) and if so, would support be indicated by different capability bit or same one ? Is that the only other one ? Currently, IB SA is using up through bit 13 and new features continue to be added (at least one more coming soon). There is some chance for feature collision if OPA would care about supporting such new IB feature if and when OPA and IB bitmasks meet with IB incrementing from bit 13 and OPA decrementing from bit 26. I wouldn't expect that to happen for a while but it would be best to anticipate this if it is of any concern to OPA. -- Hal -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
