On Sun, Nov 6, 2016 at 10:46 PM, Or Gerlitz <gerlitz.or@xxxxxxxxx> wrote: > On Sun, Nov 6, 2016 at 8:41 PM, jackm <jackm@xxxxxxxxxxxxxxxxxx> wrote: >> On Sat, 5 Nov 2016 17:03:25 -0400 >> Hal Rosenstock <hal@xxxxxxxxxxxxxxxxxx> wrote: >> >>> Isn't the SA well-known GID the concatenation of the subnet prefix >>> (which isn't necessarily the default link local one) and the GUID >>> 0x0200000000000002 ? >> >> You are correct regarding the subnet prefix (it should be the port's >> current subnet prefix, and not the default subnet prefix). >> >> Regarding the SM GUID, the version of the Virtualization Annex that I >> worked with (v17 -- Feb 16, 2015) states: >> SM GID A well-known GID that is associated with the SM, >> comprising the concatenation of the Subnet prefix and the GUID 0x2. The >> SM GID is never present in any GID Table. >> >> Has the SM GUID value changed (0x2 -->0x0200000000000002) in the Annex >> since v17? (I'm not a member of the MGTWG workgroup, so I don't have >> access to the most recent version). > > Jack, I see that in Linux we've picked the value Hal is mentioning, > see Eli Cohen's commit a0c1b2a3 "IB/core: Support accessing SA in > virtualized environment". You probably can talk to Eli to get where > things stand. yep, looking now on the annex I see the following: SM GID -- A well-known GID that is associated with the SM, comprising the concatenation of the Subnet prefix and the GUID 0x0200000000000002. The SM GID is never present in any GID Table. If the SubnetPrefix is modified by the SM, the SM GID is updated implicitly -- 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
