Hi xinze, This is mainly for reducing lock contention on a single mutex. Conditional wakeup on a mutex is expensive and that's why we wanted to make it separate from the mutex protecting Sharddata priority queue and pg_for_processing map. Are you seeing any improvement by moving to single mutex ? Thanks & Regards Somnath -----Original Message----- From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of ??? Sent: Friday, October 30, 2015 6:35 AM To: ceph-devel@xxxxxxxxxxxxxxx Subject: why we should use two Mutex in OSD ShardData? hi, all: There are two Mutex in ShardData, one is sdata_lock and the other one is sdata_op_ordering_lock. I wonder could we replace sdata_lock with sdata_op_ordering_lock? -- Regards, xinze -- 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 ��.n��������+%������w��{.n����z��u���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
