DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, mb@smartsharesystems.com,
	thomas@monjalon.net
Subject: Re: [PATCH] eal: abstract compiler atomics
Date: Tue, 31 Jan 2023 13:33:23 -0800	[thread overview]
Message-ID: <20230131213323.GA16029@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <1673558785-24992-1-git-send-email-roretzla@linux.microsoft.com>

hi folks,

just raising this to the top of mailboxes to call for reviewers. it's
going to be a lot of work by the time it's done so your feedback is
gretly appreciated.

thanks!

On Thu, Jan 12, 2023 at 01:26:24PM -0800, Tyler Retzlaff wrote:
> Introduce an abstraction for compiler specific atomics and a meson
> option to allow standard C11 atomics use.
> 
> Note, this series does not attempt to convert to the use of the
> abstraction it only introduces it as per the plan discussed here.
> http://mails.dpdk.org/archives/dev/2023-January/258693.html
> 
> devtools checkatches warnings are expected as we intend no
> functional change with this series. Subsequent series will address
> the use of __sync_xxx builtins warning.
> 
> Tyler Retzlaff (1):
>   eal: introduce atomics abstraction
> 
>  config/meson.build                     |  11 +++
>  lib/eal/arm/include/rte_atomic_32.h    |   6 +-
>  lib/eal/arm/include/rte_atomic_64.h    |   6 +-
>  lib/eal/include/generic/rte_atomic.h   | 156 ++++++++++++++++++++++++++++++++-
>  lib/eal/loongarch/include/rte_atomic.h |   6 +-
>  lib/eal/ppc/include/rte_atomic.h       |   6 +-
>  lib/eal/riscv/include/rte_atomic.h     |   6 +-
>  lib/eal/x86/include/rte_atomic.h       |   8 +-
>  meson_options.txt                      |   2 +
>  9 files changed, 199 insertions(+), 8 deletions(-)
> 
> -- 
> 1.8.3.1

  parent reply	other threads:[~2023-01-31 21:33 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 21:26 Tyler Retzlaff
2023-01-12 21:26 ` [PATCH] eal: introduce atomics abstraction Tyler Retzlaff
2023-01-31 22:42   ` Thomas Monjalon
2023-02-01  1:07     ` Honnappa Nagarahalli
2023-02-01  8:09       ` Morten Brørup
2023-02-01 21:41       ` Tyler Retzlaff
2023-02-02  8:43         ` Morten Brørup
2023-02-02 19:00           ` Tyler Retzlaff
2023-02-02 20:44             ` Morten Brørup
2023-02-03 13:56               ` Bruce Richardson
2023-02-03 14:25                 ` Morten Brørup
2023-02-03 12:19             ` Bruce Richardson
2023-02-03 20:49               ` Tyler Retzlaff
2023-02-07 15:16                 ` Morten Brørup
2023-02-07 21:58                   ` Tyler Retzlaff
2023-02-07 23:34         ` Honnappa Nagarahalli
2023-02-08  1:20           ` Tyler Retzlaff
2023-02-08  8:31             ` Morten Brørup
2023-02-08 16:35               ` Tyler Retzlaff
2023-02-09  0:16                 ` Honnappa Nagarahalli
2023-02-09  8:34                   ` Morten Brørup
2023-02-09 17:30                   ` Tyler Retzlaff
2023-02-10  5:30                     ` Honnappa Nagarahalli
2023-02-10 20:30                       ` Tyler Retzlaff
2023-02-13  5:04                         ` Honnappa Nagarahalli
2023-02-13 15:28                           ` Ben Magistro
2023-02-13 15:55                             ` Bruce Richardson
2023-02-13 16:46                               ` Ben Magistro
2023-02-13 17:49                                 ` Morten Brørup
2023-02-13 23:18                           ` Tyler Retzlaff
2023-01-31 21:33 ` Tyler Retzlaff [this message]
2023-02-08 21:43 ` [PATCH v2] eal: abstract compiler atomics Tyler Retzlaff
2023-02-08 21:43   ` [PATCH v2] eal: introduce atomics abstraction Tyler Retzlaff
2023-02-09  8:05     ` Morten Brørup
2023-02-09 18:15       ` Tyler Retzlaff
2023-02-09 19:19         ` Morten Brørup
2023-02-09 22:04           ` Tyler Retzlaff
2023-04-03 21:17       ` Mattias Rönnblom
2023-02-09  9:04     ` Bruce Richardson
2023-02-09 12:53       ` Ferruh Yigit
2023-02-09 17:40         ` Tyler Retzlaff
2023-02-09 22:13           ` Ferruh Yigit
2023-02-10  0:36             ` Tyler Retzlaff
2023-02-09 17:38       ` Tyler Retzlaff
2023-04-03 21:32         ` Mattias Rönnblom
2023-04-03 21:11     ` Mattias Rönnblom
2023-04-03 21:25       ` Honnappa Nagarahalli
2023-04-04  2:24       ` Tyler Retzlaff
2023-02-22 18:09   ` [PATCH v2] eal: abstract compiler atomics Tyler Retzlaff
2023-02-22 20:07     ` Honnappa Nagarahalli
2023-02-23 19:11       ` 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=20230131213323.GA16029@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --to=roretzla@linux.microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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).