microsoft / microsoft/mimalloc
First class heap allocations from different threads
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
I was interested in using the direct heap functions for tracking heaps directly in our codebase, but see the caveat that:
but can only allocate from the same thread that created it.
Do you have any plans on removing this restriction?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the direct heap functions and the documented same-thread allocation restriction. Read the surrounding implementation and tests to determine whether cross-thread allocation is supported by the current design. Done would require a decided approach, implementation, and coverage for heaps created in one thread and used from another.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100