Hi: Currently with user space datapath, only internal tap device can be used to communicate with kernel. Because packets must be copied from user space to kernel, the throughput of tap implementation is very slow, not suitable for data plane. Now DPDK provides some alternative solutions.
1. KNI interface. https://doc.dpdk.org/guides/nics/kni.html It requires a kernel module, and seems not well maintained. 2. Tap/Tun PMD. https://doc.dpdk.org/guides/nics/tap.html Instead of using ovs main thread to communicate with tap device, it use its own pmd thread, which may increase performance. 3. vhost+virtio adapter. https://doc.dpdk.org/guides/howto/virtio_user_as_exceptional_path.html It utilizes existing vhost and vhost-net kernel module, emulate a virtio device, communicate directly to vhost ring. This looks like a good solution. Looking for suggestions _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
