Re: ibv_req_notify_cq clarification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 22/02/2021 20:38, Hefty, Sean wrote:
>> Running this with 32 iterations, the client does something like:
>> - arm cq
>> - post send x 32
>> - wait for cq event
>> - arm cq
>> - poll cq (once, with batch size of 16)
> 
> This is a race.  The code should continue to read completions until the CQ is drained.
> 
> At this point, all completions may have been written to the CQ, and no new events will be generated.
> 
>> - no more post send (reached tot_iters)
>> - wait for cq event (but an event has already been generated?)
>>
>> And gets stuck?
> 
> - Sean
> 

That's what I suspected, but I assume people run this and it works fine on
different hardware?



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux