Jason, > Fixing the maddr table, and dealing with race issues with ongoing > joins my not be straightforward, but, IMHO, necessary for this patch > to be acceptable. >
So you are pointing out an existing bug, which is no worse with this patch than without it. Namely that pkey changes with IPv6 may have issues. IPv4 pkey changes should be ok. In any case, this patch still successfully addresses the most important requirement of having a rebooted server come up with the correct MGID. In at least the HPC world, PKey changes are extremely rare, however having server's reliably boot is important. > ipoib bonding had much the same problem with invalid maddrs, and a > patch was put in that flushed the maddr table in certain bond > scenarios. Perhaps something like that is a straightforward solution > here as well? Perhaps that could be a second patch which would build on top of this initial fix for the most important requirement. It would seem that using the PKEY change and/or re-registration HCA events to trigger a maddr flush in IPoIB would be straightforward. If that approach worked well for bonding, it should work equally well in these cases. Todd Rimmer Chief Architect QLogic Network Systems Group Voice: 610-233-4852 Fax: 610-233-4777 [email protected] www.QLogic.com -- 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
