Helps on LIBEVENT_THREAD mutex ?

This mutex seems to only exist with Storage Engine branch. We're working on prototyping a new storage engine on top of an NVRAM device. This morning, the test server hangs. Four worker threads are blocked waiting for cache_lock. The cache_lock holder is blocked in notify_io_complete() waiting for

Re: Helps on LIBEVENT_THREAD mutex ?

On Wed, Mar 14, 2012 at 11:02 AM, Wendy Cheng s.wendy.ch...@gmail.com wrote: This mutex seems to only exist with Storage Engine branch. We're working on prototyping a new storage engine on top of an NVRAM device. This morning, the test server hangs. Four worker threads are blocked waiting for

contribution preferred practices

Is there any documentation or examples on-line describing preferred form, method and criteria for offering contributions to the memcached project? My group at work has a number of significant performance improvements - some generic, some platform-specific #ifdef - we'd like to offer. However,

Re: contribution preferred practices

Is there any documentation or examples on-line describing preferred form, method and criteria for offering contributions to the memcached project? My group at work has a number of significant performance improvements - some generic, some platform-specific #ifdef - we'd like to offer.