[dpdk-dev] [PATCH v2 09/29] eal/arm64: define I/O device memory barriers for arm64

Jianbo Liu jianbo.liu at linaro.org
Tue Jan 3 08:48:32 CET 2017


On 27 December 2016 at 17:49, Jerin Jacob
<jerin.jacob at caviumnetworks.com> wrote:
> CC: Jianbo Liu <jianbo.liu at linaro.org>
> Signed-off-by: Jerin Jacob <jerin.jacob at caviumnetworks.com>
> ---
>  lib/librte_eal/common/include/arch/arm/rte_atomic_64.h | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/lib/librte_eal/common/include/arch/arm/rte_atomic_64.h b/lib/librte_eal/common/include/arch/arm/rte_atomic_64.h
> index 78ebea2..ef0efc7 100644
> --- a/lib/librte_eal/common/include/arch/arm/rte_atomic_64.h
> +++ b/lib/librte_eal/common/include/arch/arm/rte_atomic_64.h
> @@ -88,6 +88,12 @@ static inline void rte_rmb(void)
>
>  #define rte_smp_rmb() dmb(ishld)
>
> +#define rte_io_mb() rte_mb()
> +
> +#define rte_io_wmb() rte_wmb()
> +
> +#define rte_io_rmb() rte_rmb()
> +

I think it's better to use outer shareable dmb for io barrier, instead of dsb.


More information about the dev mailing list