why we use two ObjectStore::Transaction in ReplicatedBackend::submit_transaction?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hi, all:

    There are two ObjectStore::Transaction in
ReplicatedBackend::submit_transaction, one is op_t and the other one
is local_t. Is that something
    critilal logic we should consider?

    If we could reuse variable op_t it would be great. Because it is
expensive to calling local_t.append(*op_t).

    There are similar logic in ReplicatedBackend::sub_op_modify_impl.

-- 
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



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux