On Thu, Mar 9, 2017 at 7:20 PM 许雪寒 wrote:
> Thanks for your reply.
>
> As the log shows, in our test, a READ that come after a WRITE did finished
> before that WRITE.
This is where you've gone astray. Any storage system is perfectly free to
reorder simultaneous requests -- defined as those whos
Thanks for your reply.
As the log shows, in our test, a READ that come after a WRITE did finished
before that WRITE. And I read the source code, it seems that, for writes, in
ReplicatedPG::do_op method, the thread in OSD_op_tp calls
ReplicatedPG::get_rw_lock method which tries to get RWState::R
