On Thu, Jul 01, 2010 at 05:20:05PM -0700, Hefty, Sean wrote: > > The most evident example is the CM protocol, which has L2 fields in its > > payloads. > > How does moving the L3 to L2 mapping from outside create AH result > in the CM protocol needing to change? Why is hiding this under modify > QP desirable?
I'm not too sure about that either.. The concept of a reduced functionality TCA does not seem to have been considered as part of RoCE, there is nothing like APM or path selection, so it is reasonable to assume that the target in a CM can do the PR lookup equivilent to get from a GID to the L2 information. The RoCE spec does not specify that DMAC addresses must be exact match to QP data, so this is not a problem like it would be in IB. 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
