> + /* Use the hint from IP Stack to select GID Type */
> + network_gid_type = ib_network_to_gid_type(addr->dev_addr.network);
> + if (addr->dev_addr.network != RDMA_NETWORK_IB) {
> + route->path_rec->gid_type = network_gid_type;
> + /* TODO: get the hoplimit from the inet/inet6 device */
> + route->path_rec->hop_limit = IPV6_DEFAULT_HOPLIMIT;
Uh, that is more than a TODO, that is showing this is all messed up.
It isn't just the hop limit that has to come from the route entry, all
the source information of the path comes from there. Ie the gid table
should accept the route entry directly and spit out the sgid_index.
The responder side is the same, it also needs to do a route lookup to
figure out what it is doing, and that may not match what the rx says
from the headers. This is important stuff.
I really don't like the API changes that went in with the last series
that added net_dev and gid_attr everywhere, that just seems to be
enabling mistakes like the above. You can't use rocev2 without doing
route lookups, providing APIs that don't force this to happen just
encourages broken flows like this.
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
