DPDK patches and discussions
 help / color / mirror / Atom feed
From: Phil Yang <phil.yang@arm.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, ferruh.yigit@intel.com,
	hemant.agrawal@nxp.com, honnappa.nagarahalli@arm.com,
	jerinj@marvell.com, ktraynor@redhat.com,
	konstantin.ananyev@intel.com, maxime.coquelin@redhat.com,
	olivier.matz@6wind.com, stephen@networkplumber.org,
	thomas@monjalon.net, phil.yang@arm.com, ruifeng.wang@arm.com,
Subject: [dpdk-dev] [PATCH] doc: announce adoption of C11 atomic operations semantics
Date: Thu,  7 May 2020 15:06:33 +0800	[thread overview]
Message-ID: <1588835193-27550-1-git-send-email-phil.yang@arm.com> (raw)

From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>

As agreed in the DPDK tech board [1], after 20.05 release, patches must
use C11 atomic operations semantics with the help of wrappers.

[1] http://mails.dpdk.org/archives/dev/2020-April/165143.html

Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Reviewed-by: Phil Yang <phil.yang@arm.com>
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
 doc/guides/rel_notes/deprecation.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 20aa745..208708d 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -113,3 +113,15 @@ Deprecation Notices
   Python 2 support will be completely removed in 20.11.
   In 20.08, explicit deprecation warnings will be displayed when running
   scripts with Python 2.
+* rte_atomicNN_xxx: These APIs do not take memory order parameter. This does
+  not allow for writing optimized code for all the CPU architectures supported
+  in DPDK. DPDK will adopt C11 atomic operations semantics and provide wrappers
+  using C11 atomic built-ins. These wrappers must be used for patches that
+  need to be merged in 20.08 onwards.
+* rte_smp_*mb: These APIs provide full barrier functionality. However, many
+  use cases do not require full barriers. To support such use cases, DPDK will
+  adopt C11 barrier semantics and provide wrappers using C11 atomic built-ins.
+  These wrappers must be used for patches that need to be merged in 20.08
+  onwards.

             reply	other threads:[~2020-05-07  7:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  7:06 Phil Yang [this message]
2020-05-07 21:00 ` Stephen Hemminger
2020-05-08  3:46   ` Honnappa Nagarahalli
2020-05-21  4:31 ` Honnappa Nagarahalli
2020-05-21  5:04   ` Hemant Agrawal
2020-05-21  4:56 ` Jerin Jacob
2020-05-21 10:33   ` Ananyev, Konstantin
2020-05-21 19:34 ` David Christensen
2020-05-22  4:30 ` [dpdk-dev] [PATCH v2] " Honnappa Nagarahalli
2020-05-22  8:37   ` Ananyev, Konstantin
2020-05-24 23:54     ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1588835193-27550-1-git-send-email-phil.yang@arm.com \
    --to=phil.yang@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=nd@arm.com \
    --cc=olivier.matz@6wind.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \


* 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).