On Thu, Jul 15, 2010 at 01:55:32PM +0300, Liran Liss wrote: > > I objected to the draft spec leaving this area > > absent, even. > > You should submit a comment on this matter using the IBTA comment > tracker database if you intend your concern to be taken into account.
The position of IBTA is that the L2 layer is not specified as part of the spec, so of course there is no talk of how to get/create L2 information. The spec is *silent* on the issue of L2 addressing, so, IMHO, it is compltely wrong to assume it specs one approach over another, just because it omits L2 addressing related discussion/fields/etc. It, unfortunately, becomes implementation defined - and if that means an implementation chooses to extend the AH, then so be it. This is the problem with rushing incomplete specs through :) > > It wouldn't be adding another L3 itentifier it would be an L2 > > next hop MAC address for the router. It would be nice to do > > this from the start but if growing the AH is really that > > scary then it should wait until someone figures out how to > > solve the lossless routing problem on ethernet. > Augmenting the AH has a significant cost. There is a tradeoff here > between preserving the verbs api vs. dealing with the implementation > challenges associated with doing address resolution below the > verbs. The RoCE spec deliberately chooses one direction. You seem to > favor the other one. But in the interest of progress and since we > all seem to agree on the way things work when we use link local > GIDs, let us move forward with that approach for now. And we can get > back to non local GIDs later. You still have to solve the problem with vlan tags, and either each vlan interface has a seperate rdma interface or the tag has to flow into the AH from the RDMA-CM. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
