On 3/14/23 09:59, David Marchand wrote:
On Thu, Mar 9, 2023 at 1:38 PM David Marchand wrote:
In the situation when a port was started while no virtio driver was
connected, Rx interrupts were broken.
They were also broken after a virtio driver reconnects.
There were several issues mixed in:
On Thu, Mar 9, 2023 at 1:38 PM David Marchand wrote:
>
> In the situation when a port was started while no virtio driver was
> connected, Rx interrupts were broken.
> They were also broken after a virtio driver reconnects.
>
> There were several issues mixed in:
> - this driver was not exposing a
> -Original Message-
> From: David Marchand
> Sent: 2023年3月9日 20:38
> To: dev@dpdk.org
> Cc: sta...@dpdk.org; Maxime Coquelin ;
> Xia, Chenbo ; Jianfeng Tan
> ; Junjie Chen ; Hyong
> Youb Kim ; Harman Kalra
> Subject: [PATCH 3/3] net/vhost: fix Rx interrupt
>
Tested-by: Dukai Yuan
> -Original Message-
> From: David Marchand
> Sent: Thursday, March 9, 2023 8:38 PM
> To: dev@dpdk.org
> Cc: sta...@dpdk.org; Maxime Coquelin ; Xia,
> Chenbo ; Jianfeng Tan ;
> Junjie Chen ; Hyong Youb Kim ;
> Harman Kalra
> Subject: [PATCH 3/3] net/vhost: f
In the situation when a port was started while no virtio driver was
connected, Rx interrupts were broken.
They were also broken after a virtio driver reconnects.
There were several issues mixed in:
- this driver was not exposing a fixed file descriptor per Rx queue,
If a virtio driver was not co
5 matches
Mail list logo
