On Tue, Sep 30, 2014 at 10:42 AM, Somnath Roy <Somnath.Roy@xxxxxxxxxxx> wrote: > Also, I don't think this lock has big impact to performance since it is already sharded to index level. I tried with reader/writer implementation of this lock (logic will be somewhat similar to your state concept) and not getting any benefit . If there is interest in identifying locks that are introducing latency it might useful to add some tracking features to Mutex and RWLock. A simple thing would be to just record maximum wait times per lock and dump this via admin socket. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
