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.

Sign up for GitHub

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

Jump to bottom

Non-file-backed mmap() tracking #29

Closed
itamarst opened this issue Jun 26, 2020 · 1 comment · Fixed by #31
Closed

Non-file-backed mmap() tracking #29

itamarst opened this issue Jun 26, 2020 · 1 comment · Fixed by #31

Comments

@itamarst
Copy link
Collaborator

itamarst commented Jun 26, 2020 •
edited
Loading

These are effectively just allocations, though presumably larger.

Unlike free(), munmap() can deallocate some of the memory.
@itamarst itamarst mentioned this issue Jun 26, 2020
Open
3 tasks
@itamarst
Copy link
Collaborator Author

Given need for partial unmapping, probably easiest to have separate hashmap for mmap()s. And that means the auto-free() can DTRT and skip those.

This was referenced Jun 26, 2020
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Anonymous mmap() support pythonspeed/filprofiler
1 participant
@itamarst