From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: "'Mathieu Desnoyers'" <mathieu.desnoyers@efficios.com>,
"ltt-dev@lists.casi.polymtl.ca" <ltt-dev@lists.casi.polymtl.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rp@svcs.cs.pdx.edu" <rp@svcs.cs.pdx.edu>
Subject: Re: [ltt-dev] [RELEASE] Userspace RCU 0.6.0
Date: Sun, 12 Jun 2011 21:23:40 -0700 [thread overview]
Message-ID: <20110613042340.GH2212@linux.vnet.ibm.com> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB699650124A2@shsmsx502.ccr.corp.intel.com>
On Mon, Jun 13, 2011 at 10:06:09AM +0800, Cui, Dexuan wrote:
> Mathieu Desnoyers 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:
> >
> > - Added call_rcu() support, graciously contributed by Paul E.
> > McKenney.
> > - Added urcu/cds.h and merged all "Concurrent Data Containers" (CDS)
> > into a single .so: liburcu-cds.so to have a single header/shared
> > object holding all concurrency-aware data containers. It provides
> > support for RCU lists, queues and stacks at the moment.
> > - liburcu 0.6.0 now allows linking a single application with multiple
> > flavors of RCU. This required a library API change which is
> > incompatible with older 0.5.x liburcu. The .so version number
> > is therefore bumped from 0 to 1 (e.g. liburcu.so.1).
> > - Added "atfork" handling API, documented in README. Only useful for
> > processes using fork() without following exec().
> > - Renaming the following files, keeping the old files (producing a
> > compiler warning):
> > urcu/uatomic_arch.h -> urcu/uatomic.h
> > urcu/urcu-futex.h -> urcu/futex.h
> > urcu/urcu_ref.h -> urcu/ref.h
> >
> > Project website: http://lttng.org/urcu
> > Download link: http://www.lttng.org/files/urcu/
>
> Hi Mathieu,
> The release can't build in my side:
>
> $ tar -jxf userspace-rcu-0.6.0.tar.bz2 && cd userspace-rcu-0.6.0 && ./configure && make
>
> make all-recursive
> make[1]: Entering directory `/home/dcui/userspace-rcu-0.6.0'
> Making all in .
> make[2]: Entering directory `/home/dcui/userspace-rcu-0.6.0'
> CC wfqueue.lo
> CC wfstack.lo
> CC rculfqueue.lo
> CC rculfstack.lo
> CCLD liburcu-cds.la
> CC urcu.lo
> urcu.c:438:32: error: urcu-call-rcu-impl.h: No such file or directory
> urcu.c:439:29: error: urcu-defer-impl.h: No such file or directory
> make[2]: *** [urcu.lo] Error 1
> make[2]: Leaving directory `/home/dcui/userspace-rcu-0.6.0'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/dcui/userspace-rcu-0.6.0'
> make: *** [all] Error 2
>
> Can you please have a look?
I get the same thing from the tarball. But the git tree works just fine,
so my guess is that the tarball creation left out a couple of files.
Thanx, Paul
next prev parent reply other threads:[~2011-06-13 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 1:14 [RELEASE] Userspace RCU 0.6.0 Mathieu Desnoyers
2011-06-13 2:06 ` [ltt-dev] " Cui, Dexuan
2011-06-13 4:23 ` Paul E. McKenney [this message]
2011-06-13 14: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=20110613042340.GH2212@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dexuan.cui@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mathieu.desnoyers@efficios.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox