We've hit into an issue with the IB CM reject reason codes. When a remote application crashes during connection establishment, the connection will be rejected by the kernel CM. Unfortunately, there's not a decent reject reason that maps to this event. Currently, the ib_cm issues the reject as consumer defined (code 28).
I'd like to propose adding reject reason 0, which would mean other/unknown/or none given. This is a deviation from the spec, but does anyone know of any issues with such an approach? - Sean _______________________________________________ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
