From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: linux-kernel@vger.kernel.org, lttng-dev@lists.lttng.org
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [RELEASE] Userspace RCU 0.15.1
Date: Tue, 18 Feb 2025 10:51:14 -0500 [thread overview]
Message-ID: <6894741e-c3c8-4464-92ab-ba8b88929961@efficios.com> (raw)
Hi,
I've released Userspace RCU v0.15.1. The main purpose is fixing a
missing include of stdlib.h in a public header. It's a small bug, but it
caused enough issues for end users to justify a release.
liburcu is a LGPLv2.1 userspace RCU (read-copy-update) library. This
data synchronization library provides read-side access which scales
linearly with the number of cores. It does so by allowing multiple
copies of a given data structure to live at the same time, and by
monitoring the data structure accesses to detect grace periods after
which memory reclamation is possible.
liburcu-cds provides efficient data structures based on RCU and
lock-free algorithms. Those structures include hash tables, queues,
stacks, and doubly-linked lists.
Changelog:
2025-02-18 [*] Userspace RCU 0.15.1
* uatomic/generic: Add missing #include <stdlib.h>
* docs: Clarify that make is required to build the project
* fix: add missing SPDX headers to urcu/uatomic/api.h
* compiler.h: Remove caa_unqual_scalar_typeof
Project website: https://liburcu.org
Git repository: git://git.liburcu.org/urcu.git
[*] note the Changelog file in the liburcu v0.15.1 release has
2025-01-18 which is incorrect. I unfortunately noticed it too late
for the release, but it's fixed in the stable-0.15 branch for
the next release.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
reply other threads:[~2025-02-18 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6894741e-c3c8-4464-92ab-ba8b88929961@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=stern@rowland.harvard.edu \
/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