I feel that problems with packaging Concurrency Kit are solvable. If there are alternate implementations that can be selected at runtime and someone is willing to contribute code to do it I am all for it however without Concurrency Kit Ganglia is unusable for a number of larger installations and implementations.
Vladimir On 10/30/2014 09:05 PM, J.T. Conklin wrote: > Daniel Pocock <dan...@pocock.pro> writes: > >> - 3.7 adds a new dependency, Concurrency Kit > Given the problems you describe with Concurrency Kit, is it simply > premature for ganglia to depend on it? From what I can tell, its > use is isolated to lib/hash.[ch], and at first glance looks like it > an alternate reader/writer lock implementation could be selected at > runtime. Are the performance benefits of CK rwlocks really worth the > added complexity, especially as ganglia continues to depend on APR, > which also provides a rwlock implementation? > > --jtc > ------------------------------------------------------------------------------ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
