On Thu, Jan 29, 2015 at 5:05 PM, Kaushal M <[email protected]> wrote:
> Hi all, > I had started a thread previously on the efforts we are undertaking to > improve thread synchronization in GlusterD [1]. I had mentioned that we > will be using RCU for synchronization and the userspace RCU library > (liburcu) [2] for implementation. > > I am now in a almost in a position to submit changes to Gerrit for review. > But, I have an obstacle of making liburcu available on the jenkins slaves. > > I have begun development using the 0.8.6 version of liburcu, which is the > latest stable release. EPEL has liburcu packages for CentOS 6 and 7, but > they are the of the older 0.7.* versions. Fedora has packages more recent > packages, but they are still older, 0.8.1. [3]. > > Considering the above situation with binary packages, I'm considering > adding liburcu into the GlusterFS tree as a part of /contrib. This will be > similar in vein to the argp-standalone library. > > liburcu is licensed under LGPL-v2.1, so I don't think there is going to be > any problem including it. But IANAL, so I would like to know of if this > would if this is okay from a legal perspective. > > I'll add the liburcu source to our tree and push the change for review. > I'm not really familiar with autotools, so I'll need some help integrating > it into our build system. I'll update the list when I have pushed the > change for review. > How do you intend to add, as a git submodule or ? I had worked on GNU autotools in the past, but frankly don't remember much of it. If any help is needed I can try, or can get someone to help from my ex-company :) thanx, deepak
_______________________________________________ Gluster-devel mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-devel
