Hello OVS community,
OVS is packet driven and rules are configured to the data-path upon packet arrival; first packet is handled by user-space and subsequent packets are processed by the kernel data-path or by the hardware. We encounter an issue with latency sensitive protocols such as PTP/eCPRI, in which the first packet latency is far greater than subsequent ones (assuming hardware offload). ovs-dpctl utility provides the user the ability to install rules directly to the data-path, however, it is not meant to work alongside OpenFlow rules (ovs-vswitchd). Another option is to use the packet tracing functionality [1] provided by ovs-appctl. As far as I understand from the documentation, there is an option (—generate) to execute with side effects, however, it will not install a megaflow to the flow cache. Does it make sense to enhance it to support such a functionality? A warm-up interface to OVS based on a given flow-key. I’ll appreciate any feedback. This subject might have been discussed in the past. [1] https://ovs-istokes.readthedocs.io/en/latest/topics/tracing.html?highlight=trace#tracing-packets-inside-open-vswitch Cheers, Yossi Nvidia _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
