On Thu, Oct 26, 2023 at 10:10 AM Frode Nordahl <[email protected]> wrote: > > On Mon, Oct 23, 2023 at 10:19 AM David Marchand > <[email protected]> wrote: > > > > Rather than copy/paste everywhere, introduce helpers to control > > testpmd runs. > > Rely on --stats-period (which outputs port stats every n seconds) so that > > testpmd keeps running without expecting any user input. > > > > Signed-off-by: David Marchand <[email protected]> > > Acked-by: Aaron Conole <[email protected]> > > Acked-by: Eelco Chaudron <[email protected]> > > --- > > Changes since v1: > > - fixed OVS_DPDK_START_TESTPMD passed arguments evaluation:: $@ -> $1, > > Thanks for working on this, is there a plan to backport this?
I did not test extensively with earlier versions of DPDK, but I would expect it to work. I am all for getting those unit tests ran in previous branches. > > It appears that there is currently an issue with dpdk-testpmd that > makes it exit immediately when run in non-interactive mode [0], while > this is an upstream DPDK bug, it does affect the system-dpdk testsuite > for released versions of OVS. I suspect this DPDK commit broke it [1]. > > 0: https://bugs.launchpad.net/bugs/2040097 > 1: > https://github.com/DPDK/dpdk/commit/0fd1386c30c3ad9365d7fdd2829bf7cb2e1b9dff Yes [1] changed testpmd behavior. The issue seems related to the tap driver as I don't reproduce the early quit when using some other virtual driver. I opened an upstream bug: https://bugs.dpdk.org/show_bug.cgi?id=1305. -- David Marchand _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
