Remove revert_to_private_mode()
member which would require MAP_FIXED
to work reliably.
#26
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.
The reason I initially added this
revert_to_private_mode()
(so we'd load a snapshot inmapped
mode, and revert tomapped_private
mode after the snapshot is loaded), was that I hoped that we would only touch a few pages in normal mapped_private functioning.The snapshot loading seemed a bad case where all state db pages containing data would be touched.
However, even in normal syncing, most of the pages are dirty after a few minutes, so the remap optimization is not worth it I believe.
In addition, to work correctly, it would require use the linux specific
mmap(...MAP_FIXED)
api instead of the portable boost interprocess mmap interface.This PR is just unused code removal.