Re: [dpdk-dev] [PATCH v2 1/2] vdpa/mlx5: workaround FW first completion in start

2021-10-21 Thread Xueming(Steven) Li
On Thu, 2021-10-21 at 14:27 +0200, Maxime Coquelin wrote: > > On 10/15/21 17:05, Xueming Li wrote: > > After a vDPA application restart, qemu restores VQ with used and > > available index, new incoming packet triggers virtio driver to > > handle buffers. Under heavy traffic, no available buffer fo

Re: [dpdk-dev] [PATCH v2 1/2] vdpa/mlx5: workaround FW first completion in start

2021-10-21 Thread Maxime Coquelin
On 10/15/21 17:05, Xueming Li wrote: After a vDPA application restart, qemu restores VQ with used and available index, new incoming packet triggers virtio driver to handle buffers. Under heavy traffic, no available buffer for firmware to receive new packets, no Rx interrupts generated, driver

Re: [dpdk-dev] [PATCH v2 1/2] vdpa/mlx5: workaround FW first completion in start

2021-10-21 Thread Maxime Coquelin
On 10/15/21 17:05, Xueming Li wrote: After a vDPA application restart, qemu restores VQ with used and available index, new incoming packet triggers virtio driver to handle buffers. Under heavy traffic, no available buffer for firmware to receive new packets, no Rx interrupts generated, driver

[dpdk-dev] [PATCH v2 1/2] vdpa/mlx5: workaround FW first completion in start

2021-10-15 Thread Xueming Li
After a vDPA application restart, qemu restores VQ with used and available index, new incoming packet triggers virtio driver to handle buffers. Under heavy traffic, no available buffer for firmware to receive new packets, no Rx interrupts generated, driver is stuck on endless interrupt waiting. As