[openib-general] Re: [PATCH] ib_mad: prevent duplicateoutstanding MADtransactions with same TID

[Sean Hefty]

Michael S. Tsirkin wrote:
> 2. Assume vendor specific behaves in the same way as SA class, and
>    ask users to adhere to this rule

The current RMPP code actually applies this rule.  The response bit is toggled 
when sending an ACK/STOP/ABORT.

> Further if you are going to work on a spec extension, it could simply add the
> requirement on the resp bit for vendor specific classes. Right?

Correct.  Copying Hal on this message, since he's bringing up the issue with the 
IBTA.

> Sure, but again, if you initiate a request and then abort it, you
> clear the response bit, if you are receiving a request and decide to abort it,
> you set the response bit.
> 
> Therefore if you get an abort you can look at the resp bit: if it is
> set this is a transaction that you initiated, if it is clear this is
> a transaction that remote side initiated.
> 
> I conclude that there's no ambiguity. Am I mistaken?

I believe that you're correct, but I need to consider this more with respect to 
receiving a duplicated request, while a response is being generated.

- Sean