New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optimize clone write path if object-map is enabled #6403
Conversation
@xinxinsh I would initialize your "object exists" variable (named with |
b36f390
to
89ce1da
Compare
46c200a
to
6338253
Compare
m_state = LIBRBD_AIO_WRITE_GUARD; | ||
complete(-ENOENT); | ||
} else { | ||
m_state = LIBRBD_AIO_WRITE_FLAT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I think about this more, perhaps we should keep the guarded write in the case just to be extra-safe. That would allow you to combine this block with the "m_object_exists" condition block.
bdde6eb
to
2430b0f
Compare
@dillaman , updated, help review |
Fixes : ceph#13500 Signed-off-by: xinxin shu <xinxin.shu@intel.com>
Signed-off-by: xinxin shu <xinxin.shu@intel.com>
3c78d7d
to
33aabf2
Compare
@dillaman , updated |
LGTM -- I'll run it through tests tomorrow |
optimize clone write path if object-map is enabled Reviewed-by: Jason Dillaman <dillaman@redhat.com>
Fixes : #13500
Signed-off-by: xinxin shu xinxin.shu@intel.com