> If this is the case, how would we fix the problem ? It's hard for us to > delay to destroy the QP, because we don't know how long to delay. > The other way is to do something from the driver, or firmware.
I think you just have to deal with this possibility at your level. This type of thing is just inherent in network programming: without an explicit message back, you don't know if any given message has really been received. The exact same thing could happen with TCP for example: just cut the cable after a message has been received but before the ACK has gone back the other way. - R. _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
