os/bluestore: _dump_onode() don't prolongate Onode anymore. #19841
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before the patch
BlueStore::_dump_onode()
takesOnodeRef
by value effectively extending the object's life time.This is unnecessary and can be costly as
BlueStore::OnodeRef
is ref-counted withboost::intrusive_ptr
. Moreover, callers are supposed to already hold a reference, so the optimization forcount == 0
case stays without effect of inhibiting call toBlueStore::Onode::put()
and atomic integer increment.Signed-off-by: Radoslaw Zarzynski rzarzyns@redhat.com