Re: [lttng-dev] [RFC] Deprecating RCU signal flavor

After discussing it with Mathieu, we agree on the following 3 phases for
deprecating the signal flavor:

 1) liburcu-signal will be implemented in term of liburcu-mb. The only
 difference between the two flavors will be the public header files,
 linked symbols and library name.  Note that this add a regression in
 term of performance, since the implementation of liburcu-mb adds memory
 barriers on the reader side which are not present in the original
 liburcu-signal implementation.

 2) Adding the deprecated attribute to every public functions exposed by
 the liburcu-signal flavor.  At this point, tests for liburcu-signal
 will also be removed from the project.  There will be no more support
 for this flavor.

 3) Removing the liburcu-signal flavor completely from the project.

Finally, here is a tentative versions release of mine for each phase:

 1) 0.15.0 [October 2023] (also TSAN support yay!)

 2) 0.15.1

 3) 0.16.0 || 1.0.0 (maybe a major bump since this is an API breaking
 change)

-- 
Olivier Dion
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev