Re: [dpdk-dev] [PATCH v3] eal: use c11 atomic built-ins for interrupt status

2020-07-10 Thread Dodji Seketeli
David Marchand writes: [...] >> --- a/devtools/libabigail.abignore >> +++ b/devtools/libabigail.abignore >> @@ -48,6 +48,10 @@ >> changed_enumerators = RTE_CRYPTO_AEAD_LIST_END >> [suppress_variable] >> name = rte_crypto_aead_algorithm_strings >> +; Ignore updates of epoll eve

Re: [dpdk-dev] [PATCH v3] eal: use c11 atomic built-ins for interrupt status

2020-07-09 Thread David Marchand
On Thu, Jul 9, 2020 at 10:35 AM Phil Yang wrote: > > The event status is defined as a volatile variable and shared between > threads. Use c11 atomic built-ins with explicit ordering instead of > rte_atomic ops which enforce unnecessary barriers on aarch64. > > The event status has been cleaned up

Re: [dpdk-dev] [PATCH v3] eal: use c11 atomic built-ins for interrupt status

2020-07-09 Thread David Marchand
On Thu, Jul 9, 2020 at 10:35 AM Phil Yang wrote: > > The event status is defined as a volatile variable and shared between > threads. Use c11 atomic built-ins with explicit ordering instead of > rte_atomic ops which enforce unnecessary barriers on aarch64. > > The event status has been cleaned up

[dpdk-dev] [PATCH v3] eal: use c11 atomic built-ins for interrupt status

2020-07-09 Thread Phil Yang
The event status is defined as a volatile variable and shared between threads. Use c11 atomic built-ins with explicit ordering instead of rte_atomic ops which enforce unnecessary barriers on aarch64. The event status has been cleaned up by the compare-and-swap operation when we free the event data