Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: "Ondřej Surý via lttng-dev" <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev@lists.lttng.org, paulmck <paulmck@kernel.org>
Subject: Re: [lttng-dev] userspace-rcu and ThreadSanitizer
Date: Fri, 17 Mar 2023 18:02:28 +0100	[thread overview]
Message-ID: <F524C7BA-80C2-42C0-A5EA-697833761DA3@sury.org> (raw)
In-Reply-To: <3b41f7b2-401f-6455-e6e2-a9bfeeabe93d@efficios.com>

> On 17. 3. 2023, at 14:44, Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> 
> I would indeed like to remove all the custom atomics assembly code from liburcu now that there are good atomics support in the major compilers (gcc and clang). 

Here's very preliminary implementation:

https://gitlab.isc.org/isc-projects/userspace-rcu/-/merge_requests/2

I just did something wrong somewhere along the path and it doesn't compile now,
but it did for me locally.

I am submitting this now as it's 18:00 Friday evening and my kids are starting to
be angry at me :).

This will need some more work - I think some of the cmm_ macros might be dropped
now, and somebody who does that more often than I should take a look at the memory
orderings.

Ondrej
--
Ondřej Surý (He/Him)
ondrej@sury.org

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2023-03-17 17:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 12:26 Ondřej Surý via lttng-dev
2023-03-17 13:44 ` Mathieu Desnoyers via lttng-dev
2023-03-17 15:50   ` Ondřej Surý via lttng-dev
2023-03-17 16:10     ` Mathieu Desnoyers via lttng-dev
2023-03-17 17:02   ` Ondřej Surý via lttng-dev [this message]
2023-03-17 18:56     ` Mathieu Desnoyers via lttng-dev
2023-03-17 16:57 ` Duncan Sands via lttng-dev

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=F524C7BA-80C2-42C0-A5EA-697833761DA3@sury.org \
    --to=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=ondrej@sury.org \
    --cc=paulmck@kernel.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