m ; Mykola Kostenok
; Serhii Iliushyk
*Копия:* step...@networkplumber.org ;
dev@dpdk.org ; Chenbo Xia
*Тема:* Re: [PATCH v4 1/1] vhost: handle virtqueue locking for memory
hotplug
Hi Danylo,
On 6/4/25 10:32 AM, Danylo Vodopianov wrote:
Hello, Maxime
Thank you for your review.
If I unders
.com
; mcoqu...@redhat.com ; Christian Koue
Muf ; ma...@mellanox.com ;
david.march...@redhat.com ; Mykola Kostenok
; Serhii Iliushyk
Копия: step...@networkplumber.org ; dev@dpdk.org
; Chenbo Xia
Тема: Re: [PATCH v4 1/1] vhost: handle virtqueue locking for memory hotplug
Hi Danylo,
On 6/
;
dev@dpdk.org ; Chenbo Xia
*Тема:* Re: [PATCH v4 1/1] vhost: handle virtqueue locking for memory
hotplug
Hello Danylo,
On 6/2/25 10:50 AM, Danylo Vodopianov wrote:
For vDPA devices, virtqueues are not locked once the device has been
configured. In the
commit 5e8fcc60b59d ("vhost: enha
lumber.org ; dev@dpdk.org
; Chenbo Xia
Тема: Re: [PATCH v4 1/1] vhost: handle virtqueue locking for memory hotplug
Hello Danylo,
On 6/2/25 10:50 AM, Danylo Vodopianov wrote:
> For vDPA devices, virtqueues are not locked once the device has been
> configured. In the
> commit 5e8fcc60b5
Hello Danylo,
On 6/2/25 10:50 AM, Danylo Vodopianov wrote:
For vDPA devices, virtqueues are not locked once the device has been
configured. In the
commit 5e8fcc60b59d ("vhost: enhance virtqueue access lock asserts"),
the asserts were enhanced to trigger rte_panic functionality, preventing
access
For vDPA devices, virtqueues are not locked once the device has been
configured. In the
commit 5e8fcc60b59d ("vhost: enhance virtqueue access lock asserts"),
the asserts were enhanced to trigger rte_panic functionality, preventing
access to virtqueues without locking. However, this change introduce
6 matches
Mail list logo
