[ceph-users] why lock th whole osd handle thread

[baijia...@126.com]

when I see the function OSD::OpWQ::_process . I find pg lock locks the whole 
function. so when I  use multi-thread write the same object , so are they must 
serialize from osd handle thread to journal write thread ?



baijia...@126.com___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] why lock th whole osd handle thread

[Gregory Farnum]

On Thu, Jul 3, 2014 at 8:24 AM, baijia...@126.com baijia...@126.com wrote:
 when I see the function OSD::OpWQ::_process . I find pg lock locks the
 whole function. so when I  use multi-thread write the same object , so are
 they must
 serialize from osd handle thread to journal write thread ?

It's serialized while processing the write, but that doesn't include
the wait time for the data to be placed on disk — merely sequencing it
and feeding it into the journal queue. Writes have to be ordered, so
that's not likely to change.
-Greg
Software Engineer #42 @ http://inktank.com | http://ceph.com
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com