[lttng-dev] [RFC] Planning a release of the RCU lock-free hash table
dgoulet at ev0ke.net
Fri Feb 17 11:06:41 EST 2012
-----BEGIN PGP SIGNED MESSAGE-----
We are using it quite a lot in lttng-tools and no problem at all for now. During
the implementation period (in lttng-tools) bugs were reported and usability
issues like the "for_each_entry" macros. It's been a couple of month now without
I can't speak for stability/scalability but I do vouch for the *usefulness* for
a lot of other projects! If you feel that it's stable enough, go for it. More
user, more fixes.
On 12-02-17 10:56 AM, Mathieu Desnoyers wrote:
> I wanted to ask around if the general feeling is that the API of the RCU
> lock-free hash table is stable enough to be pulled into the master
> branch of userspace rcu ? Are there any further changes to the API any
> of you would envision ?
> Link to the current API:
> My personal thought is that after the restructuring, cleanup and fixes
> from Lai, and review from Paul and Stephen, things have been quiet for a
> few months, so it might be a good time to plan for a release.
> Pointer to the rcu lock-free hash table branch:
> git://git.lttng.org/userspace-rcu.git branch: urcu/ht-shrink
> It will be a _very_ nice addition to the userspace RCU library, as the
> uses of this lock-free hash table are many (think of routing, dns,
> parallel answer to network queries "pinned" to worker threads, etc..).
> This hash table is, IMHO, better than the Java lock-free hash table,
> mainly because the RCU lock-free hash table offers ordering guarantees
> over the modifications operations vs lookups and iteration.
> Thoughts ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the lttng-dev