Skip to content
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

os/bluestore: use iterator for erase() method directly #11490

Merged
merged 1 commit into from Oct 14, 2016

Conversation

xiexingguo
Copy link
Member

No description provided.

@ifed01
Copy link
Contributor

ifed01 commented Oct 14, 2016

Looks like there is duplicate write_onode call for _do_truncate and _do_clone_range too.

@ifed01
Copy link
Contributor

ifed01 commented Oct 14, 2016

I'm not completely sure if this duplication's worth fixing but I'd prefer to have ALL write_onode calls at the same level for the sake of uniformity, i.e. either at entry points (_zero, _truncate, _clone, etc) or at some underlying ones (_do_zero, _do_truncate, _do_clone_range, etc). Just IMHO though...

Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>
@xiexingguo xiexingguo changed the title os/bluestore: a few more cleanups os/bluestore: use iterator for erase() method directly Oct 14, 2016
@xiexingguo
Copy link
Member Author

@ifed01 I am with you.

Dropped that change.

@ifed01 ifed01 merged commit d04eee8 into ceph:master Oct 14, 2016
@liewegas
Copy link
Member

@ifed01 @xiaoxichen agreed on being consistent. Probably do*.... in a handful of cases that will include a duplicate insert, but it's probably safer? No strong preference though.

@xiexingguo xiexingguo deleted the xxg-wip-bluestore-1014 branch October 14, 2016 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants