Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Duncan Sands via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] [RFC] Deprecating RCU signal flavor
Date: Thu, 11 May 2023 08:57:11 +0200	[thread overview]
Message-ID: <59232ffe-de85-9c7c-d3b7-70def1437476@free.fr> (raw)
In-Reply-To: <87v8gzuc3g.fsf@laura>

Hi Olivier, we (DeepBlueCapital) gave up on urcu-signal a long time ago, due to 
the annoying side effects signals can have.  Nowadays we use membarrier, so 
removing urcu-signal is fine as far as we are concerned.

Best wishes, Duncan.

On 10/05/2023 23:10, Olivier Dion via lttng-dev wrote:
> Hi all,
> 
> We have the intention of deprecating the urcu-signal flavor in the
> future.  We are asking users of URCU for _feedback_ on this before
> going any further.
> 
> Part of this decision is that we are adding support for TSAN in URCU and
> the signal flavor deadlocks with TSAN.  It is also my understanding that
> the urcu-signal flavor was historically made as a fallback for system
> lacking the membarrier(2) system call.  Nowadays, most systems have
> support for that system call, making the urcu-signal an artifact of the
> past.
> 
> The following is a proposed timeline of events:
> 
>    1. Asking for feedback from users of URCU (this message)
>    2. Disabling the signal flavor by default and adding --enable-flavor-signal
>    3. Removing the signal flavor
> 

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

  reply	other threads:[~2023-05-11  7:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 21:10 Olivier Dion via lttng-dev
2023-05-11  6:57 ` Duncan Sands via lttng-dev [this message]
2023-05-16 12:16 ` Paul E. McKenney via lttng-dev
2023-05-16 13:11 ` Ondřej Surý via lttng-dev
2023-08-14 21:05 ` Olivier Dion via lttng-dev
2023-08-15 12:38   ` Mathieu Desnoyers via lttng-dev
2023-08-21 15:43     ` Mathieu Desnoyers via lttng-dev
2023-08-23 14:47       ` Paul E. McKenney via lttng-dev
2023-08-23 14:52         ` Mathieu Desnoyers 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=59232ffe-de85-9c7c-d3b7-70def1437476@free.fr \
    --to=lttng-dev@lists.lttng.org \
    --cc=baldrick@free.fr \
    /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