From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Tyler Retzlaff" <roretzla@linux.microsoft.com>, <dev@dpdk.org>
Cc: <Honnappa.Nagarahalli@arm.com>, <Ruifeng.Wang@arm.com>,
<thomas@monjalon.net>
Subject: RE: [PATCH 0/3] use C11 memory model GCC builtin atomics
Date: Mon, 27 Mar 2023 17:25:16 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D8780F@smartserver.smartshare.dk> (raw)
In-Reply-To: <1679927420-26737-1-git-send-email-roretzla@linux.microsoft.com>
> From: Tyler Retzlaff [mailto:roretzla@linux.microsoft.com]
> Sent: Monday, 27 March 2023 16.30
>
> Replace the use of __sync_<op>_and_fetch and __sync_fetch_and_<op> atomics
> with GCC C11 memory model __atomic builtins.
>
> This series contributes to converging on standard atomics in 23.11 but is
> kept separate as there may be sensitivity to converting from __sync to the
> C11 memory model builtins.
>
> Tyler Retzlaff (3):
> bus/vmbus: use C11 memory model GCC builtin atomics
> crypto/ccp: use C11 memory model GCC builtin atomics
> eal: use C11 memory model GCC builtin atomics
>
> drivers/bus/vmbus/vmbus_channel.c | 2 +-
> drivers/crypto/ccp/ccp_dev.c | 6 ++++--
> lib/eal/include/generic/rte_atomic.h | 32 ++++++++++++++++----------------
> 3 files changed, 21 insertions(+), 19 deletions(-)
>
> --
> 1.8.3.1
>
Series-reviewed-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2023-03-27 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:30 Tyler Retzlaff
2023-03-27 14:30 ` [PATCH 1/3] bus/vmbus: " Tyler Retzlaff
2023-03-27 14:30 ` [PATCH 2/3] crypto/ccp: " Tyler Retzlaff
2023-03-27 14:30 ` [PATCH 3/3] eal: " Tyler Retzlaff
2023-03-27 15:25 ` Morten Brørup [this message]
2023-05-24 12:51 ` [PATCH 0/3] " David Marchand
2023-05-24 16:05 ` Tyler Retzlaff
2023-06-02 4:18 ` Tyler Retzlaff
2023-06-07 16:36 ` David Marchand
2023-06-07 16:46 ` 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=98CBD80474FA8B44BF855DF32C47DC35D8780F@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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).