From: gmack@innerfire.net (Gerhard Mack)
Subject: [lttng-dev] [RELEASE] Userspace RCU 0.7.3
Date: Wed, 27 Jun 2012 10:36:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1206271033210.25860@mtl.rackplans.net> (raw)
In-Reply-To: <20120627133523.GA13831@Krystal>
Yes, it looks like it does. Sorry for the noise it looks like it picked
up debian''s 6.7.2 rather than the newer version.
Gerhard
On Wed, 27 Jun 2012, Mathieu Desnoyers wrote:
> Date: Wed, 27 Jun 2012 09:35:24 -0400
> From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> To: Gerhard Mack <gmack at innerfire.net>
> Cc: Alexandre Montplaisir <alexandre.montplaisir at polymtl.ca>,
> lttng-dev at lists.lttng.org
> Subject: Re: [RELEASE] Userspace RCU 0.7.3
>
> * Gerhard Mack (gmack at innerfire.net) wrote:
> >
> > Just a heads up, I had to add the following to get it working with code
> > compiled with the gcc flag "-std=c99"
> >
> > #ifndef asm
> > #define asm __asm
> > #endif
>
> Normally, in userspace rcu git master HEAD, you have this commit
> already:
>
> commit e51500edbd9919cee53bc85cbb4b22cd4786fc42
> Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> Date: Tue Jun 12 11:24:31 2012 -0400
>
> Fix c99 compatibility: use __asm__ and __volatile__ in public headers
>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
>
> Does it fix it for you ?
>
> Thanks,
>
> Mathieu
>
> >
> > Gerhard
> >
> > On Mon, 4 Jun 2012, Mathieu Desnoyers wrote:
> >
> > > Date: Mon, 4 Jun 2012 11:51:43 -0400
> > > From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > > To: Gerhard Mack <gmack at innerfire.net>,
> > > Alexandre Montplaisir <alexandre.montplaisir at polymtl.ca>
> > > Cc: lttng-dev at lists.lttng.org
> > > Subject: Re: [RELEASE] Userspace RCU 0.7.3
> > >
> > > * Gerhard Mack (gmack at innerfire.net) wrote:
> > > >
> > > > Are there any online examples of how to use this library? I can't seem to
> > > > find any.
> > >
> > > The perfbook from Paul McKenney now uses userspace RCU in its examples
> > > (http://kernel.org/pub/linux/kernel/people/paulmck/perfbook/perfbook.html)
> > >
> > > Also, you will find various small programs in the source tree of the
> > > userspace-rcu packages under tests/ that act as test programs, and also
> > > show how to use the library. (in the git tree:
> > > http://git.lttng.org/?p=userspace-rcu.git;a=tree;f=tests;hb=HEAD)
> > >
> > > I guess setting up a tutorial HTML page from the test content would be
> > > valuable, we just have not had the time to do it at this point. Maybe
> > > setting up links to that documentation on the lttng.org/urcu web page
> > > would be a good start though.
> > >
> > > Alexandre, when you find a minute, can you look into this ?
> > >
> > > Thanks!
> > >
> > > Mathieu
> > >
> > >
> > > >
> > > > Gerhard
> > > >
> > > >
> > > >
> > > > On Fri, 1 Jun 2012, Mathieu Desnoyers wrote:
> > > >
> > > > > Date: Fri, 1 Jun 2012 14:05:33 -0400
> > > > > From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > > > > To: linux-kernel at vger.kernel.org, lttng-dev at lists.lttng.org,
> > > > > rp at svcs.cs.pdx.edu
> > > > > Cc: Paul E. McKenney <paulmck at linux.vnet.ibm.com>,
> > > > > Lai Jiangshan <laijs at cn.fujitsu.com>,
> > > > > Stephen Hemminger <shemminger at vyatta.com>
> > > > > Subject: [RELEASE] Userspace RCU 0.7.3
> > > > >
> > > > > 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.
> > > > >
> > > > > liburcu-cds provides efficient data structures based on RCU and
> > > > > lock-free algorithms. Those structures include hash tables, queues,
> > > > > stacks, and doubly-linked lists.
> > > > >
> > > > > This is a minor compatibility-related release, fixing build issues with
> > > > > FreeBSD and NetBSD. On Linux, only the test_perthreadlock fix could
> > > > > change the result of make check (which could previously fail due to
> > > > > non-initialized mutexes), but it does not impact anything installed on
> > > > > the system.
> > > > >
> > > > > Changelog:
> > > > > 2012-06-01 Userspace RCU 0.7.3
> > > > > * Fix tests: make dist lib dependency
> > > > > * Update README for OS supported, tests dependency
> > > > > * Add CodingStyle to tarball
> > > > > * Add coding style document
> > > > > * Test fix: test_perthreadlock uninitialized mutex
> > > > > * tests: support FreeBSD short "time" args
> > > > > * freebsd 8.2 fix: define MAP_ANONYMOUS for compatibility
> > > > >
> > > > > Project website: http://lttng.org/urcu
> > > > > Download link: http://lttng.org/files/urcu/
> > > > >
> > > > >
> > > >
> > > > --
> > > > Gerhard Mack
> > > >
> > > > gmack at innerfire.net
> > > >
> > > > <>< As a computer, I find your faith in technology amusing.
> > >
> > >
> >
> > --
> > Gerhard Mack
> >
> > gmack at innerfire.net
> >
> > <>< As a computer, I find your faith in technology amusing.
>
>
--
Gerhard Mack
gmack at innerfire.net
<>< As a computer, I find your faith in technology amusing.
next prev parent reply other threads:[~2012-06-27 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 18:05 Mathieu Desnoyers
[not found] ` <alpine.DEB.2.02.1206040932580.2583@mtl.rackplans.net>
2012-06-04 15:51 ` Mathieu Desnoyers
[not found] ` <alpine.DEB.2.02.1206270608320.25860@mtl.rackplans.net>
2012-06-27 13:35 ` Mathieu Desnoyers
2012-06-27 14:36 ` Gerhard Mack [this message]
2012-06-27 16:02 ` 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=alpine.DEB.2.02.1206271033210.25860@mtl.rackplans.net \
--to=gmack@innerfire.net \
/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