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

chore: use memmap2 instead of mapr #1624

Merged
merged 1 commit into from
Aug 22, 2022
Merged

chore: use memmap2 instead of mapr #1624

merged 1 commit into from
Aug 22, 2022

Conversation

vmx
Copy link
Contributor

@vmx vmx commented Aug 12, 2022

memmap2 is maintained and contains all features from mapr, so using
the mapr fork of memmap is no longer needed.

Here are the changes in detail:

  • map_anon() in memmap2 is always MAP_PRIVATE, so a call to private()
    is no longer needed.
  • using mlock is similar to the MAP_LOCKED setting, hence it is no longer
    set. In memmap2 the mlock() is just called lock().
  • MAP_PRIVATE is done via map_copy_read_only().

Copy link
Contributor

@storojs72 storojs72 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I believe it is good to merge this PR after this one - #1625 that fixes Darwin CI job execution. Plus it looks like we can now archive https://github.com/filecoin-project/mapr repository as it is not used anymore. Who can do that (I cannot unfortunately...)? May be @dignifiedquire ?

`memmap2` is maintained and contains all features from `mapr`, so using
the `mapr` fork of `memmap` is no longer needed.

Here are the changes in detail:

 - `map_anon()` in `memmap2` is always `MAP_PRIVATE`, so a call to `private()`
is no longer needed.
 - using `mlock` is similar to the `MAP_LOCKED` setting, hence it is no longer
   set. In `memmap2` the `mlock()` is just called `lock()`.
 - `MAP_PRIVATE` is done via `map_copy_read_only()`.
@vmx vmx merged commit 39e4302 into master Aug 22, 2022
@vmx vmx deleted the memmap2 branch August 22, 2022 13:28
@vmx vmx mentioned this pull request Aug 22, 2022
vmx added a commit that referenced this pull request Sep 15, 2022
`memmap2` is maintained and contains all features from `mapr`, so using
the `mapr` fork of `memmap` is no longer needed.

Here are the changes in detail:

 - `map_anon()` in `memmap2` is always `MAP_PRIVATE`, so a call to `private()`
is no longer needed.
 - using `mlock` is similar to the `MAP_LOCKED` setting, hence it is no longer
   set. In `memmap2` the `mlock()` is just called `lock()`.
 - `MAP_PRIVATE` is done via `map_copy_read_only()`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants