Hi Jack,
Thanks so much for the really quick response. This is very helpful..
Please find my answers below:
> This simply indicates that the VF did not receive a command-completion
> interrupt.
>
So, in this case, I think that VF didn't receive a command-completion
interrupt for the NOP command.
On Wed, 31 Dec 2014 02:26:07 +0530
Bob Biloxi wrote:
> Hi,
>
> I was going through the mlx4 source code and had a few questions
> regarding the generation of interrupts upon execution of the NOP
> command from the VF driver.
>
> If i am running as a dedicated driver, then NOP seems to work fine
