net/mlx5: mitigate Rx doorbell memory barrier
authorMatan Azrad <matan@mellanox.com>
Thu, 30 May 2019 10:20:34 +0000 (10:20 +0000)
committerFerruh Yigit <ferruh.yigit@intel.com>
Thu, 13 Jun 2019 15:01:06 +0000 (00:01 +0900)
commit6cfb15300607fd74669cb66f77f418755b80c86f
tree077c5578072dd750082ce145b9d1649769f1d441
parent15b0ea00535d4e164891168ef628b112ae049e06
net/mlx5: mitigate Rx doorbell memory barrier

The RQ WQEs must be written in the memory before the HW gets the RQ
doorbell, hence a memory barrier should be triggered after the WQEs
writing and before the doorbell writing.

The current code used rte_wmb barrier which ensures that all the memory
stores were done while it is enough to use rte_cio_wmb barrier for the
local memory stores because the WQEs are in local memory.

CC: stable@dpdk.org
Signed-off-by: Matan Azrad <matan@mellanox.com>
Acked-by: Shahaf Shuler <shahafs@mellanox.com>
drivers/net/mlx5/mlx5_rxq.c