Stanislaw Kardach 6cda39af86 test/distributor: fix burst flush on worker quit
While working on RISC-V port I have encountered a situation where worker
threads get stuck in the rte_distributor_return_pkt() function in the
burst test.
Investigation showed some of the threads enter this function with
flag RTE_DISTRIB_GET_BUF set in the d->retptr64[0]. At the same time the
main thread has already passed rte_distributor_process() so nobody will
clear this flag and hence workers can't return.

What I've noticed is that adding a flush just after the last _process(),
similarly to how quit_workers() function is written in the
test_distributor.c fixes the issue.
Lukasz Wojciechowski reproduced the same issue on x86 using a VM with 32
emulated CPU cores to force some lcores not to be woken up.

Fixes: 7c3287a10535 ("test/distributor: add performance test for burst mode")
Cc: stable@dpdk.org

Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
Acked-by: David Hunt <david.hunt@intel.com>
Tested-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
Reviewed-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
2021-05-05 18:21:26 +02:00
..
2020-10-02 13:51:00 +02:00
2021-04-21 16:29:20 +02:00
2019-02-26 15:29:27 +01:00
2020-10-19 16:08:36 +02:00
2021-04-21 17:08:02 +02:00
2019-02-26 15:29:27 +01:00
2019-02-26 15:29:27 +01:00
2019-02-26 15:29:27 +01:00
2019-12-20 15:05:41 +01:00
2020-10-13 19:26:15 +02:00
2021-03-03 10:05:23 +01:00
2020-10-20 13:17:08 +02:00
2020-02-05 14:37:41 +01:00
2019-02-26 15:29:27 +01:00
2019-07-06 10:32:34 +02:00
2020-10-28 21:23:11 +01:00
2020-03-04 10:11:07 +01:00
2020-10-28 21:23:11 +01:00
2020-10-24 11:11:46 +02:00
2020-04-25 15:15:30 +02:00
2019-10-23 16:57:06 +02:00
2021-04-26 15:33:07 +02:00
2021-03-16 20:15:29 +01:00
2020-07-08 14:41:06 +02:00
2021-04-09 14:01:07 +02:00
2020-02-05 14:37:41 +01:00
2019-02-26 15:29:27 +01:00
2020-02-05 14:37:41 +01:00
2021-01-14 16:41:40 +01:00
2020-04-16 18:16:46 +02:00
2020-02-05 14:37:41 +01:00
2019-04-11 14:27:32 +02:00
2019-10-27 14:40:55 +01:00
2019-02-26 15:29:27 +01:00
2020-10-16 22:26:41 +02:00
2019-02-26 15:29:27 +01:00
2019-02-26 15:29:27 +01:00
2019-11-26 00:12:08 +01:00
2019-11-07 17:46:43 +01:00
2020-11-15 16:45:48 +01:00
2019-02-26 15:29:27 +01:00
2019-02-26 15:29:27 +01:00
2019-02-26 15:29:27 +01:00
2019-02-26 15:29:27 +01:00
2021-04-20 23:13:23 +02:00
2019-02-26 15:29:27 +01:00
2021-04-14 15:14:56 +02:00
2021-04-14 15:14:56 +02:00