Re: [dpdk-dev] [PATCH v1 0/8] use GCC's C11 atomic builtins for test
From: Stephen Hemminger <stephen@networkplumber.org>
Date: 2021-06-04 19:57:25
On Fri, 4 Jun 2021 04:46:16 -0500 Joyce Kong [off-list ref] wrote:
Since C11 memory model is adopted in DPDK now[1], use GCC's atomic builtins in test cases. [1]https://www.dpdk.org/blog/2021/03/26/dpdk-adopts-the-c11-memory-model/ Joyce Kong (8): test/ticketlock: use GCC atomic builtins for lcores sync test/spinlock: use GCC atomic builtins for lcores sync test/rwlock: use GCC atomic builtins for lcores sync test/mcslock: use GCC atomic builtins for lcores sync test/mempool: remove unused variable for lcores sync test/mempool_perf: use GCC atomic builtins for lcores sync test/service_cores: use GCC atomic builtins for lock sync test/rcu_perf: use GCC atomic builtins for data sync app/test/test_mcslock.c | 13 +++-- app/test/test_mempool.c | 5 -- app/test/test_mempool_perf.c | 12 ++--- app/test/test_rcu_qsbr_perf.c | 98 +++++++++++++++++------------------ app/test/test_rwlock.c | 9 ++-- app/test/test_service_cores.c | 36 +++++++------ app/test/test_spinlock.c | 10 ++-- app/test/test_ticketlock.c | 9 ++-- 8 files changed, 93 insertions(+), 99 deletions(-)
Thanks, I did this for pflock tests during review cycle Acked-by: Stephen Hemminger <stephen@networkplumber.org>