[dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead of asm volatile

2014-02-04 Thread Thomas Monjalon
30/01/2014 12:42, Hiroshi Shimamoto: > > Use the DPDK specific function rte_mb() instead of > > the GCC statement asm volatile ("" ::: "memory"). > > > > Signed-off-by: Olivier Matz > > Yes, that's preferred for DPDK, I think. > Looks okay to me. Applied, thanks. -- Thomas

[dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead of asm volatile

2014-01-31 Thread Olivier MATZ
Hi Hiroshi-san, On 01/30/2014 12:42 PM, Hiroshi Shimamoto wrote: >> Subject: [dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead >> of asm volatile > > By the way, I was also asked to use rte atomic function > instead of cmpxchg asm statement. > My re-submi

[dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead of asm volatile

2014-01-30 Thread Hiroshi Shimamoto
> Subject: [dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead > of asm volatile > > Use the DPDK specific function rte_mb() instead of > the GCC statement asm volatile ("" ::: "memory"). Yes, that's preferred for DPDK, I think. Looks okay t

[dpdk-dev] [memnic PATCH] pmd: use memory barrier function instead of asm volatile

2014-01-24 Thread Olivier Matz
Use the DPDK specific function rte_mb() instead of the GCC statement asm volatile ("" ::: "memory"). Signed-off-by: Olivier Matz --- common/memnic.h | 2 -- pmd/pmd_memnic.c | 6 +++--- 2 files changed, 3 insertions(+), 5 deletions(-) diff --git a/common/memnic.h b/common/memnic.h index