From: Dharmik Thakkar <dharmik.thakkar@arm.com>
Cc: dev@dpdk.org, nd@arm.com, honnappa.nagarahalli@arm.com,
ruifeng.wang@arm.com, joyce.kong@arm.com,
dharmik.thakkar@arm.com
Subject: [dpdk-dev] [PATCH v3 0/8] use compiler atomic builtins for examples
Date: Wed, 13 Oct 2021 13:53:59 -0500 [thread overview]
Message-ID: <20211013185407.2841183-1-dharmik.thakkar@arm.com> (raw)
In-Reply-To: <20210823054952.15001-1-joyce.kong@arm.com>
Since atomic operations have been adopted in DPDK now[1],
change rte_atomicNN_xxx APIs to compiler's atomic built-ins
in examples module[2].
[1] https://www.dpdk.org/blog/2021/03/26/dpdk-adopts-the-c11-memory-model/
[2] https://doc.dpdk.org/guides/rel_notes/deprecation.html
v3:
Keep rte_atomic.h in examples/vhost_blk/vhost_blk.c (Chenbo)
v2:
Fix the compiling error of performance-thread patch.
Joyce Kong (8):
examples/bbdev_app: use compiler atomics for flag sync
examples/multi_process: use compiler atomics for sync
examples/kni: use compiler atomics for status sync
examples/performance-thread: use compiler atomics for sync
examples/l2fwd-jobstats: use compiler atomics for stats sync
examples/vm_power_manager: use compiler atomics for sync
examples/server_node_efd: use compiler atomics for sync
examples: remove unnecessary include of atomic
examples/bbdev_app/main.c | 13 ++++---
examples/bond/main.c | 1 -
examples/ip_fragmentation/main.c | 1 -
examples/ip_reassembly/main.c | 1 -
examples/ipsec-secgw/ipsec-secgw.c | 1 -
examples/ipv4_multicast/main.c | 1 -
examples/kni/main.c | 27 +++++++--------
examples/l2fwd-crypto/main.c | 1 -
examples/l2fwd-event/l2fwd_common.h | 1 -
examples/l2fwd-event/l2fwd_event.c | 1 -
examples/l2fwd-jobstats/main.c | 11 +++---
examples/l2fwd-keepalive/main.c | 1 -
examples/l2fwd/main.c | 1 -
examples/l3fwd-acl/main.c | 1 -
examples/l3fwd-power/main.c | 1 -
examples/l3fwd/main.c | 1 -
examples/link_status_interrupt/main.c | 1 -
.../client_server_mp/mp_client/client.c | 1 -
.../client_server_mp/mp_server/init.c | 1 -
.../client_server_mp/mp_server/main.c | 7 ++--
examples/multi_process/simple_mp/main.c | 1 -
.../multi_process/simple_mp/mp_commands.c | 1 -
examples/multi_process/symmetric_mp/main.c | 1 -
examples/performance-thread/common/lthread.c | 10 +++---
.../performance-thread/common/lthread_diag.h | 10 +++---
.../performance-thread/common/lthread_int.h | 1 -
.../performance-thread/common/lthread_mutex.c | 26 +++++++-------
.../performance-thread/common/lthread_mutex.h | 2 +-
.../performance-thread/common/lthread_sched.c | 34 ++++++++-----------
.../performance-thread/common/lthread_tls.c | 5 +--
.../performance-thread/l3fwd-thread/main.c | 22 +++++-------
examples/server_node_efd/node/node.c | 1 -
examples/server_node_efd/server/init.c | 1 -
examples/server_node_efd/server/main.c | 7 ++--
examples/vhost_blk/blk.c | 1 -
examples/vm_power_manager/channel_manager.c | 1 -
examples/vm_power_manager/channel_manager.h | 1 -
examples/vm_power_manager/channel_monitor.c | 11 +++---
examples/vmdq/main.c | 1 -
examples/vmdq_dcb/main.c | 1 -
40 files changed, 91 insertions(+), 121 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2021-10-13 18:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 5:49 [dpdk-dev] [PATCH v2 " Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 1/8] examples/bbdev_app: use compiler atomics for flag sync Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 2/8] examples/multi_process: use compiler atomics for sync Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 3/8] examples/kni: use compiler atomics for status sync Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 4/8] examples/performance-thread: use compiler atomics for sync Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 5/8] examples/l2fwd-jobstats: use compiler atomics for stats sync Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 6/8] examples/vm_power_manager: use compiler atomics for sync Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 7/8] examples/server_node_efd: " Joyce Kong
2021-08-23 5:49 ` [dpdk-dev] [PATCH v2 8/8] examples: remove unnecessary include of atomic Joyce Kong
2021-08-23 11:29 ` Xia, Chenbo
2021-08-24 2:30 ` Joyce Kong
2021-10-13 18:53 ` Dharmik Thakkar [this message]
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 1/8] examples/bbdev_app: use compiler atomics for flag sync Dharmik Thakkar
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 2/8] examples/multi_process: use compiler atomics for sync Dharmik Thakkar
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 3/8] examples/kni: use compiler atomics for status sync Dharmik Thakkar
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 4/8] examples/performance-thread: use compiler atomics for sync Dharmik Thakkar
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 5/8] examples/l2fwd-jobstats: use compiler atomics for stats sync Dharmik Thakkar
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 6/8] examples/vm_power_manager: use compiler atomics for sync Dharmik Thakkar
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 7/8] examples/server_node_efd: " Dharmik Thakkar
2021-10-13 18:54 ` [dpdk-dev] [PATCH v3 8/8] examples: remove unnecessary include of atomic Dharmik Thakkar
2021-10-15 23:30 ` Dharmik Thakkar
2021-10-19 15:12 ` David Marchand
2021-10-19 15:12 ` [dpdk-dev] [PATCH v3 0/8] use compiler atomic builtins for examples David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211013185407.2841183-1-dharmik.thakkar@arm.com \
--to=dharmik.thakkar@arm.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=joyce.kong@arm.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).