On Thu, Jul 08, 2021 at 03:02:34PM +0100, Cian Ferriter wrote: > From: Harry van Haaren <harry.van.haa...@intel.com> > > This commit adds a new command to allow the user to switch > the active DPIF implementation at runtime. A probe function > is executed before switching the DPIF implementation, to ensure > the CPU is capable of running the ISA required. For example, the > below code will switch to the AVX512 enabled DPIF assuming > that the runtime CPU is capable of running AVX512 instructions: > > $ ovs-appctl dpif-netdev/dpif-impl-set dpif_avx512 > > A new configuration flag is added to allow selection of the > default DPIF. This is useful for running the unit-tests against > the available DPIF implementations, without modifying each unit test. > > The design of the testing & validation for ISA optimized DPIF > implementations is based around the work already upstream for DPCLS. > Note however that a DPCLS lookup has no state or side-effects, allowing > the auto-validator implementation to perform multiple lookups and > provide consistent statistic counters. > > The DPIF component does have state, so running two implementations in > parallel and comparing output is not a valid testing method, as there > are changes in DPIF statistic counters (side effects). As a result, the > DPIF is tested directly against the unit-tests. > > Signed-off-by: Harry van Haaren <harry.van.haa...@intel.com> > Co-authored-by: Cian Ferriter <cian.ferri...@intel.com> > Signed-off-by: Cian Ferriter <cian.ferri...@intel.com> > > ---
Acked-by: Flavio Leitner <f...@sysclose.org> _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
