All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: linux-kernel@vger.kernel.org, lttng-dev@lists.lttng.org,
	rp@svcs.cs.pdx.edu
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: [RELEASE] Userspace RCU 0.7.15 and 0.8.8
Date: Wed, 9 Sep 2015 18:10:26 +0000 (UTC)	[thread overview]
Message-ID: <886050080.2087.1441822226486.JavaMail.zimbra@efficios.com> (raw)

Hi,

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.

Those are bugfix releases for stable-0.7 and stable-0.8 branches.
Small fixes to the tests (volatile in assert() and out of tree test
fix) were not backported to stable-0.7 due to important changes
to the test tree layout between 0.7 and 0.8.

Changelog:
2015-09-09 Userspace RCU 0.7.15
        * Disable sys_membarrier
        * uatomic: Specify complete types for atomic function calls
        * Fix: handle sys_futex() FUTEX_WAIT interrupted by signal
        * Fix: compat_futex.c: *uaddr should be read as volatile
        * Fix: call_rcu_thread() affinity failure
        * urcu: fix deprecation warning with new glibc

2015-09-09 Userspace RCU 0.8.8
        * Disable sys_membarrier
        * Fix: volatile in assert()
        * uatomic: Specify complete types for atomic function calls
        * Fix: handle sys_futex() FUTEX_WAIT interrupted by signal
        * Fix: compat_futex.c: *uaddr should be read as volatile
        * Fix: make benchmark test run in oot build
        * Fix: call_rcu_thread() affinity failure
        * urcu: fix deprecation warning with new glibc

Project website: http://liburcu.org
Git repository: git://git.liburcu.org/urcu.git

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

                 reply	other threads:[~2015-09-09 18:10 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=886050080.2087.1441822226486.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rp@svcs.cs.pdx.edu \
    --cc=shemminger@vyatta.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.