Quoting r. Or Gerlitz <[EMAIL PROTECTED]>: > Subject: Re: [PATCH] ib_cm: randomize starting local comm IDs > > On 8/22/06, Sean Hefty <[EMAIL PROTECTED]> wrote: > > Randomize the starting local comm ID to avoid getting a rejected connection > > due to a stale connection after a system reboot or reloading of the ib_cm. > > Hi Sean, > > I have tested the patch against an iser target based on our Gen1 CM - > it works as expected. > > So the CM at the target side rejects the first REQ after the client > reboot with STALE reason (and deliveres a disconnect event to the > ULP). The second REQ is processed fine and a new connection is > established. > > Without the patch, since the REQ had <local_id,qpn> as this of an > existing connection, it was just silently dropped and a target reboot > was a must to let the initiator reconnect ! > > Or.
Hmm. Might this still be a concern for users such as SDP which don't retry connections? -- MST _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
