Re: kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue

Michael, Thank you very much for your help. I greatly appreciate it. Steven On 12/17/18, 4:16 PM, "Michael S. Tsirkin" wrote: On Mon, Dec 17, 2018 at 11:56:59PM +, Steven Luong (sluong) wrote: > > > On 12/17/18, 2:55 PM, "Michael S. Tsirkin" wrote: > > On

Re: kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue

On 12/17/18, 2:55 PM, "Michael S. Tsirkin" wrote: On Thu, Dec 13, 2018 at 11:24:28PM +, Steven Luong (sluong) via Virtualization wrote: > Folks, > > > > We came across a memory race condition between VPP vhost driver and the kernel > vhost. VPP is running

Re: kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue

On Thu, Dec 13, 2018 at 11:24:28PM +, Steven Luong (sluong) via Virtualization wrote: > Folks, > > > > We came across a memory race condition between VPP vhost driver and the kernel > vhost. VPP is running a tap interface over vhost backend. In this case, VPP is > acting as the vhost

kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue

Folks, We came across a memory race condition between VPP vhost driver and the kernel vhost. VPP is running a tap interface over vhost backend. In this case, VPP is acting as the vhost driver mode and the kernel vhost is acting as the vhost device mode. In the kernel vhost’s TX traffic