Quoting r. Sean Hefty <[EMAIL PROTECTED]>: > Subject: Re: [openib-general] Re: [PATCH] ib_mad: prevent > duplicateoutstanding MADtransactions with same TID > > Jack Morgenstein wrote: > >Which session actually receives the ACK is a toss-up, since when a session > >sends a segment, it is placed (upon send completion) at the tail of the > >wait queue. Thus, arriving ACKs will likely be routed (based upon TID > >only) to one of the duplicate sessions. > > Okay - this makes more sense. Thanks for the clarification.
Okay - so the proposed fix is to simply prevent duplicate transactions returning an error code to the user. This is similiar to the patch that Jack sent, only we have to add the GID, class, and method resp bit check. -- Michael S. Tsirkin Staff Engineer, Mellanox Technologies _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
