All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Josh Triplett <josh@joshtriplett.org>,
	Jon Bernard <jbernard@debian.org>, Jan Blunck <jblunck@suse.de>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Pierre Habouzit <madcoder@debian.org>,
	Steven Munroe <munroesj@linux.vnet.ibm.com>,
	Bert Wesarg <bert.wesarg@googlemail.com>,
	Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>
Cc: linux-kernel@vger.kernel.org, rp@svcs.cs.pdx.edu,
	ltt-dev@lists.casi.polymtl.ca
Subject: [RELEASE] Userspace RCU library (liburcu) 0.2
Date: Thu, 1 Oct 2009 09:56:11 -0400	[thread overview]
Message-ID: <20091001135611.GA12323@Krystal> (raw)
In-Reply-To: <20090929210951.GC28427@Krystal>

Hi,

Here is a 0.2 version of the urcu library. It should clarify usage of

rcu_cmpxchg_pointer
rcu_xchg_pointer
rcu_set_pointer

which are the recommended primitives to deal with pointers.
rcu_assign_pointer(ptr, new) is provided as compatibility layer with the
Linux kernel semantic, but note that its semantic for the first
parameter is IMHO odd and differs from rcu_{cmpxchg,xchg,set}_pointer.

Website URL:
http://lttng.org/urcu

Direct link to the package:
http://www.lttng.org/files/urcu/userspace-rcu-0.2.tar.gz

Thanks,

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2009-10-01 14:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 21:09 [RELEASE] Userspace RCU library (liburcu) 0.1 Mathieu Desnoyers
2009-10-01 13:56 ` Mathieu Desnoyers [this message]
2009-10-02 17:05   ` [RELEASE] Userspace RCU library (liburcu) 0.2.1 Mathieu Desnoyers
2009-10-05 22:08     ` [RELEASE] Userspace RCU library (liburcu) 0.2.2 Mathieu Desnoyers
2009-10-07 21:50       ` Userspace RCU library, now with autotools Mathieu Desnoyers
2009-10-08  5:24         ` 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=20091001135611.GA12323@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=bert.wesarg@googlemail.com \
    --cc=jbernard@debian.org \
    --cc=jblunck@suse.de \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=madcoder@debian.org \
    --cc=munroesj@linux.vnet.ibm.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pierre-marc.fournier@polymtl.ca \
    --cc=rp@svcs.cs.pdx.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.