From: jbernard@debian.org (Jon Bernard)
Subject: [ltt-dev] [RELEASE] Userspace RCU 0.4.7
Date: Fri, 24 Sep 2010 12:31:34 -0400 [thread overview]
Message-ID: <20100924163132.GA6101@starquasia> (raw)
In-Reply-To: <20100922201830.GB7669@Krystal>
* Mathieu Desnoyers <mathieu.desnoyers at efficios.com> wrote:
> 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 multiples 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.
>
> Changelog for Userspace RCU 0.4.7:
>
> - Add wait-free enqueue/push, blocking dequeue/pop list and stack.
> - Add lock-free enqueue/dequeue/push/pop list and stack.
> - Add ifdef around container_of() definition to kill gcc warnings when building
> UST.
>
> The wait-free enqueue/blocking dequeue will enable creation of the call_rcu()
> primitive in a near future.
The 0.4.7 tarball is missing 'urcu/urcu_ref.h', causing the following
error:
CC rculfqueue.lo
In file included from rculfqueue.c:26:
urcu/rculfqueue.h:26:22: error: urcu_ref.h: No such file or directory
In file included from rculfqueue.c:26:
urcu/rculfqueue.h:45: error: field ?ref? has incomplete type
In file included from rculfqueue.c:27:
urcu/rculfqueue-static.h:29:27: error: urcu/urcu_ref.h: No such file or directory
--
Jon
next prev parent reply other threads:[~2010-09-24 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 20:18 Mathieu Desnoyers
2010-09-24 16:31 ` Jon Bernard [this message]
2010-09-24 20:50 ` Mathieu Desnoyers
2010-09-24 21:06 ` [ltt-dev] [RELEASE] Userspace RCU 0.4.8 Mathieu Desnoyers
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=20100924163132.GA6101@starquasia \
--to=jbernard@debian.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