On 2/6/21 5:15 PM, William Tu wrote: > On Mon, Feb 1, 2021 at 5:48 PM Yi Yang (杨燚)-云服务集团 <[email protected]> wrote: >> >> Thanks Ilya, net_tap PMD is handling tap device on host side, so it can >> leverage vnet header to do TSO/GSO, maybe net_pmd authors don't know how to >> do this, from source code, tap fd isn't enabled vnet header and TSO. >> > thanks, learned a lot from these discussions. > > I looked at the DPDK net_tap and indeed it doesn't support virtio net hdr. > Do you guys think it makes sense to add TSO at dpdk net_tap? > Or simply using the current OVS's userspace-enable-tso on tap/veth is > good enough? > (using type=system, not using dpdk port type on tap/veth.) > > Regards, > William >
I didn't benchmark all types of interfaces, but I'd say that, if you need more or less high performance solution for userspace<->kernel communication, you should, probably, take a look at virtio-user ports with vhost kernel backend: https://doc.dpdk.org/guides/howto/virtio_user_as_exceptional_path.html This should be the fastest and also feature-rich solution. Tap devices are not designed for high performance in general, so I'd not suggest any of them for highly loaded ports. If it's only for some small management traffic, it should be fine to just use netdev-linux implementation. netdev-afxdp with pmd or non-pmd modes on a veth devices is another (potentially high performance) solution. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
