From: Stephen Hemminger <shemminger@vyatta.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org, lttng-dev@lists.lttng.org,
rp@svcs.cs.pdx.edu,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RELEASE] Userspace RCU 0.7.6
Date: Thu, 10 Jan 2013 08:57:54 -0800 [thread overview]
Message-ID: <20130110085754.2d32b314@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20130110164241.GA5051@Krystal>
On Thu, 10 Jan 2013 11:42:41 -0500
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> * Stephen Hemminger (shemminger@vyatta.com) wrote:
> > On Wed, 9 Jan 2013 13:46:17 -0500
> > Mathieu Desnoyers <mathieu.desnoyers@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.
> > >
> > > 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 bugfix release, mainly fixing handling of processes using
> > > call_rcu, then fork() without following exec(), and then continuing use
> > > of synchronize_rcu() or call_rcu() in the child process. A hang in
> > > synchronize_rcu() in the child could occur, which is fixed by this
> > > release.
> > >
> > > Changelog:
> > > 2013-01-09 Userspace RCU 0.7.6
> > > * Discourage use of pthread_atfork() for call_rcu handlers
> > > * Fix call_rcu fork handling
> > > * test: fork handling
> > > * Fix TLS detection: test with linker, add --disable-compiler-tls
> > > * Cleanup: cast pthread_self() return value to unsigned long
> > > * Fallback mechanism not working on platform where TLS is unsupported
> > >
> > > Project website: http://lttng.org/urcu
> > > Download link: http://lttng.org/files/urcu/
> > >
> >
> > Why is the git repository still at 0.7.4 and there is no tag for 0.7.6?
> > Am I looking at the right place?
> > $ git remote -v
> > origin git://git.lttng.org/userspace-rcu.git (fetch)
>
> I tried doing this to confirm:
>
> git clone git://git.lttng.org/userspace-rcu.git
> cd userspace-rcu
> git tag -l
>
> and v0.7.6 is there.
>
> Please note that this tag is in the stable-0.7 branch (not master).
>
> Please let me know if the problem persists for you after making sure you
> use the right branch.
>
> Thanks,
>
> Mathieu
>
Ok, I didn't see the stable branch.
prev parent reply other threads:[~2013-01-10 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 18:46 [RELEASE] Userspace RCU 0.7.6 Mathieu Desnoyers
2013-01-10 16:32 ` Stephen Hemminger
2013-01-10 16:42 ` Mathieu Desnoyers
2013-01-10 16:57 ` Stephen Hemminger [this message]
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=20130110085754.2d32b314@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rp@svcs.cs.pdx.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).