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-trivial shared-memory allocator #19

Open
lars-t-hansen opened this issue Feb 3, 2015 · 1 comment
Open

Non-trivial shared-memory allocator #19

lars-t-hansen opened this issue Feb 3, 2015 · 1 comment
Labels
enhancement High priority

Comments

@lars-t-hansen
Copy link
Owner

We should provide an allocator for shared memory that also allows for memory to be freed.

It should be API compatible with the bump allocator's core API (allocation methods and array accessors, but no mark or release). However, reliable heap sizing will probably be impossible for the new allocator, as there will need to be some overhead to track object sizes, and there will be overhead from fragmentation if anything is freed.
@lars-t-hansen lars-t-hansen mentioned this issue Feb 3, 2015
Open
@lars-t-hansen
Copy link
Owner Author

Work on this is going on on the branch "allocator".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement High priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lars-t-hansen