* Ingo Molnar ([email protected]) wrote: > > [ ... ] > > > > All that aside, one advantage of http://lttng.org/urcu is that it > > already exists, which allows prototyping to proceed immediately. > > it's offline right now: > > $ git clone git://git.lttng.org/urcu > Cloning into urcu... > fatal: The remote end hung up unexpectedly
This would be: git clone git://git.lttng.org/userspace-rcu.git I'll make sure a symlink for urcu -> userspace-rcu.git gets setup shortly. > One complication is that it's LGPL while tools/kvm/ is GPLv2. I guess > we could copy a suitable implementation into tools/kvm/rcu/? That might make sense, yes. The intent of having liburcu LGPL is really to give as much liberty for apps developers to link to it as they have calling Linux kernel system calls. This peculiarness of the GPL Linux is able to use to let non-GPL apps use it does not apply so clearly to libraries, hence the use of LGPL for all my libs that support application execution. Thanks, Mathieu -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
