Re: [PATCH] net/virtio: fix socket nonblocking mode affects initialization

On 6/17/22 04:42, Yuan Wang wrote: The virtio-user initialization requires unix socket to receive backend messages in block mode. However, vhost_user_update_link_state() sets the same socket to nonblocking via fcntl, which affects all threads. Enabling the rxq interrupt can causes both of thes

RE: [PATCH] net/virtio: fix socket nonblocking mode affects initialization

> -Original Message- > From: Wang, YuanX > Sent: Friday, June 17, 2022 10:42 AM > To: maxime.coque...@redhat.com; Xia, Chenbo ; > dev@dpdk.org > Cc: Hu, Jiayu ; He, Xingguang ; > Wang, YuanX ; sta...@dpdk.org > Subject: [PATCH] net/virtio: fix socket

Re: [PATCH] net/virtio: fix socket nonblocking mode affects initialization

On Fri, 17 Jun 2022 10:42:29 +0800 Yuan Wang wrote: > The virtio-user initialization requires unix socket to receive backend > messages in block mode. However, vhost_user_update_link_state() sets > the same socket to nonblocking via fcntl, which affects all threads. > Enabling the rxq interrupt c

[PATCH] net/virtio: fix socket nonblocking mode affects initialization

The virtio-user initialization requires unix socket to receive backend messages in block mode. However, vhost_user_update_link_state() sets the same socket to nonblocking via fcntl, which affects all threads. Enabling the rxq interrupt can causes both of these behaviors to occur concurrently, with