Hi Ilya,

> -----Original Message-----
> From: Ilya Maximets <[email protected]>
> Sent: Thursday, September 16, 2021 1:27 AM
> To: Pai G, Sunil <[email protected]>; [email protected]
> Cc: Richardson, Bruce <[email protected]>; Mcnamara, John
> <[email protected]>; [email protected]; Hu, Jiayu
> <[email protected]>; [email protected]
> Subject: Re: [ovs-dev] [PATCH RFC dpdk-latest V2 0/1] Enable vhost async
> API's in OvS.
> 
> On 9/7/21 14:00, Sunil Pai G wrote:
> > This series brings in the new asynchronous vHost API's in DPDK to OVS.
> > With the asynchronous framework, vHost-user can offload the memory
> > copy operation to DPDK DMA-dev based enabled devices like IntelĀ®
> > QuickData Technology without blocking the CPU.
> 
> Copying here what I accidentally sent in reply to v1.
> ---
> 
> As said in reply to the 'deferral of work' patch-set, OVS is synchronous and 
> it
> is fine, because network devices are asynchronous by their nature.
> OVS is not blocked by memory copies, because these are handled by DMA
> configured and handled by device drivers. This patch adds DMA handling to

As you said, network devices are asynchronous by nature and OVS is unaware of 
it.
For vhost, do you suggest that OVS shouldn't be aware of if vhost is 
asynchronous?
In other words, OVS shouldn't change code to asynchronous style. Is that 
correct?

Thanks,
Jiayu

> vhost, making it essentially a physical device at some extent, but for some
> reason driver for that is implemented inside OVS.  High level application
> should not care about memory copies inside the physical device and DMA
> configuration, but the code in this patch looks very much as parts of a
> specific device driver.
> 
> Implementation of this feature belongs to vhost library, which is a driver for
> this (now) physical device.  This way it can be consumed by OVS or any other
> DPDK application without major code changes.
> 
> Best regards, Ilya Maximets.
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to