DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: honnappa.nagarahalli@arm.com
Cc: ferruh.yigit@intel.com, david.marchand@redhat.com, dev@dpdk.org,
	phil.yang@arm.com, techboard@dpdk.org
Subject: [dpdk-dev] Using C11 atomic semantic
Date: Mon, 20 Jul 2020 17:34:01 +0200	[thread overview]
Message-ID: <7124002.r8JxatOC3Q@thomas> (raw)

In the techboard of April 22, it has been decided to block patches
using rte_atomicNN_xx and rte_smp_*mb APIs, starting DPDK 20.08.
Meeting minutes:
Deprecation notice:

Some doc has been submitted to help understanding how to manage atomics:
	http://doc	.dpdk.org/guides/prog_guide/writing_efficient_code.html#locks-and-atomic-operations

Unfortunately the tool to check new code was merged last week:

As a consequence, I propose to apply the "reject rule" starting DPDK 20.11.

Can we make this rule better advertised with an announce message?
Are the current technical explanations enough?
If not, it would be wonderful to have a blog post explaining the details,
as part of an announce.

             reply	other threads:[~2020-07-20 15:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 15:34 Thomas Monjalon [this message]
2020-07-20 15:44 ` Honnappa Nagarahalli
2020-07-20 16:39   ` Thomas Monjalon
2020-07-20 19:36     ` Honnappa Nagarahalli

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=7124002.r8JxatOC3Q@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=phil.yang@arm.com \
    --cc=techboard@dpdk.org \


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