[ovs-dev] [PATCH RFC dpdk-latest V2 0/1] Enable vhost async API's in OvS.

[Ilya Maximets]

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 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.