-----Original Message---- > This relates back to the question on whether a port has > more than one address. It depends on your definition of a > port. If the definition of a port is a netdevice then it > is only necessary to provide one of the addresses. Existing > techniques allow fetching the other aliases that refer to > the same ethernet interface. There is no reason for the RDMA > drivers to take on the complexity of reporting all possible > IP addresses when the answer already exists in for non-RDMA.
My comment was in reference to the iwcm_port structure, which maps to a physical port on the device. I can't say that I understand the use of the local_addr field in that structure. - Sean ---------- No it doesn't map to the physical port, it just typically maps to a physical port. It maps to an L2 endpoint. The ethernet portion of the device may be doing binding. In either case, the L2 endpoint can have multiple IP addresses, but it always has a primary IP address. iWARP rides on top of IP. Any solutions in place, such as teaming of ports, will generally remain in place. The definitions MUST allow this. As noted earlier, the RDMA layer should not really know the MAC address, just the IP address. Knowing the MAC address, however, turns out to be pretty harmless. Knowing the "true" physical port, however, is a very different matter. _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
