Hi Ilya, > -----Original Message----- > From: Ilya Maximets <[email protected]> > Sent: Wednesday, September 15, 2021 8:52 PM > To: Pai G, Sunil <[email protected]>; [email protected] > Cc: [email protected]; Maxime Coquelin <[email protected]> > Subject: Re: [ovs-dev] [PATCH RFC dpdk-latest 0/1] netdev-dpdk: Enable > DPDK vHost async API's > > On 10/23/20 11:48, 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 operations to the hardware like Intel® QuickData Technology without > blocking the CPU. > > > > This series also attempts to highlight noteable issues associated with > > enabling asynchronous data path in OVS. > > > > Currently OVS seems to be quite synchronous in nature in terms of packet > data path. > > This poses a problem in implementing the async data path as there > > doesnt seem to be a clean way to free the packets at a later point in time > without breaking abstractions. > > Which is why the free for asynchronously sent packets is currently done at > the dpif level per PMD. > > 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.
Thanks for the review. A recent version of the patch with a different architecture was published here : http://patchwork.ozlabs.org/project/openvswitch/list/?series=261277 It would be of great help if we could get your inputs/feedback on that one too. Thanks and regards, Sunil _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
