> But, how could RDMA CM work? Inbound CM messages will be filtered if > the IP is not in the HW GID table? I'm not understanding the issue. If a device has some requirement to program its assigned IP addresses into some HW table, I don't see why upper layers should be made to care. The IB CM is essentially handling 2 different type of CM messages -- one for IB and one for RoCE. This just adds a third type. All three types are similar, with some fields ignored and others formatted using different data. The CM interface can be updated to better reflect reality, rather than pretending that RoCE has path records or anything other than IB-classic has LIDs. The CM message definitions themselves could also be updated to indicate which fields matter. > How could UD work? I haven't given much thought to UD, but since AV creation goes directly to the driver, I still don't see why GIDs need to be used. The driver can encode whatever it needs to (e.g. GID/IP index) into the AV. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
