Quoting r. Sean Hefty <[EMAIL PROTECTED]>: > Subject: Re: [PATCH] ib_mad: prevent duplicateoutstanding MADtransactions > with same TID > > >I dont see a way around this: the dirt is at the spec level. > > Correct - I believe this is an architectural issue that needs to be > addressed by changes to the spec.
Okay. But, note this affects ACKs as well as ABORTs (with multi-packet requests): Host A sends an RMPP request message to host B with TID=3 Host B sends an RMPP request message to host A with TID=3. Now if A generates an RMPP response it has TID=3. If B sends ACK, host A has no idea which transaction is being ACKed. What kind of spec change do you envision? -- 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
