Publish worker parameters with a release fence before launching the
lcores instead of the deprecated SMP write barrier.

Signed-off-by: Stephen Hemminger <[email protected]>
---
 drivers/event/dpaa2/dpaa2_eventdev_selftest.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/event/dpaa2/dpaa2_eventdev_selftest.c 
b/drivers/event/dpaa2/dpaa2_eventdev_selftest.c
index 9d4938efe6..12c1bc9878 100644
--- a/drivers/event/dpaa2/dpaa2_eventdev_selftest.c
+++ b/drivers/event/dpaa2/dpaa2_eventdev_selftest.c
@@ -524,7 +524,7 @@ launch_workers_and_wait(int (*main_worker)(void *),
        param[0].sched_type = sched_type;
        param[0].port = 0;
        param[0].dequeue_tmo_ticks = dequeue_tmo_ticks;
-       rte_smp_wmb();
+       rte_atomic_thread_fence(rte_memory_order_release);
 
        w_lcore = rte_get_next_lcore(
                        /* start core */ -1,
@@ -537,7 +537,7 @@ launch_workers_and_wait(int (*main_worker)(void *),
                param[port].sched_type = sched_type;
                param[port].port = port;
                param[port].dequeue_tmo_ticks = dequeue_tmo_ticks;
-               rte_smp_wmb();
+               rte_atomic_thread_fence(rte_memory_order_release);
                w_lcore = rte_get_next_lcore(w_lcore, 1, 0);
                rte_eal_remote_launch(workers, &param[port], w_lcore);
        }
-- 
2.53.0

Reply via email to