From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org
Subject: RFC abstracting atomics
Date: Mon, 9 Jan 2023 14:56:04 -0800 [thread overview]
Message-ID: <20230109225604.GA25566@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
hi folks,
i would like to introduce a layer of abstraction that would allow
optional use of standard C11 atomics when the platform / toolchain
combination has them available.
making the option usable would be a phased approach intended to focus
review and minimize dealing with churn on such a broad change.
1. provide an initial series to add the abstraction and the ability
control enablement with a meson option enable_stdatomics=false will
be the default.
for all existing platform / toolchain combinations the default would
remain false. i.e. i have no plans to enable it for existing platforms
toolchain combinations but leaves a change of default open to the
community as a future discussion if it is desired.
2. once the initial abstraction is integrated a series will be introduced to
port the tree to the abstraction with enable_stdatomics=false. the goal
being low or no change to the current use of gcc builtin C++11 memory
model atomics.
3. once the tree is ported a final series will be introduced to introduce
the remaining change to allow the use of enable_stdatomics=true.
would appreciate any assistance / suggestions you can provide to
introduce the abstraction smoothly.
thanks
next reply other threads:[~2023-01-09 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 22:56 Tyler Retzlaff [this message]
2023-01-10 9:16 ` Bruce Richardson
2023-01-10 11:45 ` Morten Brørup
2023-01-10 20:31 ` Tyler Retzlaff
2023-01-11 7:45 ` Morten Brørup
2023-01-10 20:10 ` Tyler Retzlaff
2023-01-11 10:10 ` Bruce Richardson
2023-01-11 10:23 ` Morten Brørup
2023-01-11 11:56 ` Bruce Richardson
2023-01-11 12:46 ` Morten Brørup
2023-01-11 14:18 ` Bruce Richardson
2023-01-11 15:07 ` Morten Brørup
2023-01-13 14:18 ` Ben Magistro
2023-01-13 16:10 ` Jerin Jacob
2023-01-13 17:17 ` Tyler Retzlaff
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=20230109225604.GA25566@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=dev@dpdk.org \
/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).