On 1/28/19 7:55 AM, sunwenjie wrote:
When rte_vhost_driver_unregister delete the connection fd,
fdset_try_del will always try and donot release the
vhostuser.mutex if the fd is busy, but the fdset_event_dispatch
will set the fd to busy and call vhost_user_msg_handler to get
vhostuser.mutex,
Thanks, Maxime.
Your description is better, My real name is Wenjie Sun.
Signed-off-by: Wenjie Sun
Maxime Coquelin 于2019年2月8日周五 下午10:12写道：
>
>
> On 1/28/19 7:55 AM, sunwenjie wrote:
> > When rte_vhost_driver_unregister delete the connection fd,
> > fdset_try_del will always try and donot rele
On 1/28/19 7:55 AM, sunwenjie wrote:
When rte_vhost_driver_unregister delete the connection fd,
fdset_try_del will always try and donot release the
vhostuser.mutex if the fd is busy, but the fdset_event_dispatch
will set the fd to busy and call vhost_user_msg_handler to get
vhostuser.mutex,
When rte_vhost_driver_unregister delete the connection fd,
fdset_try_del will always try and donot release the
vhostuser.mutex if the fd is busy, but the fdset_event_dispatch
will set the fd to busy and call vhost_user_msg_handler to get
vhostuser.mutex, which will cause deadlock. Unlock the
vho
Hi,
On 01/11, sunwenjie wrote:
>When rte_vhost_driver_unregister delete the connection fd,
>fdset_try_del will always try and donot release the
>vhostuser.mutex if the fd is busy, but the fdset_event_dispatch
>will set the fd to busy and call vhost_user_msg_handler to get
>vh
When rte_vhost_driver_unregister delete the connection fd,
fdset_try_del will always try and donot release the
vhostuser.mutex if the fd is busy, but the fdset_event_dispatch
will set the fd to busy and call vhost_user_msg_handler to get
vhostuser.mutex, which will cause dead
6 matches
Mail list logo
