RE: When IBoE will be merged to upstream?

Hefty, Sean
2010-06-24T18:05:30Z

> Regarding GID to Eth mappings, we discussed using the standard create_ah()
> Verb for this.
> In the kernel, create_ah() will call a generic address resolution function
> in the cma.
> The returned information will be copied back to user-space in a device-
> specific structure (since address handles are device-specific).
>
> This eliminates adding a new get_eth_l2_addr() ABI call (device-specific or
> not).
> In fact, this approach eliminates adding new ABIs for any kind of address
> translation...
>
> Does this seem reasonable?

The current behavior of ibv_create_ah() requires that the caller provide the L2, and if needed, L3 addressing. Any translation between the L3 and L2 addressing must be done before the call is made. E.g. ibv_create_ah does not use the GID to query the SA to obtain LIDs. Why doesn't IBoE follow this same model?

Callers can use some out of band mechanism for the mapping, call rdma_resolve_addr, or use some standard networking routine.