microsoft / microsoft/mimalloc
Lock-freeness
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
I noticed there was a mention of mimalloc being lock-free in #265, but I don't know if that still holds. The reason is that I would like to use this in an audio application with the huge page size setting so that allocation and deallocation of my data structures happen in deterministic time.
I would like to know if it is still true that mimalloc is lock-free and if it is safe to assume that allocations and deallocations happen in deterministic time with the huge page size setting. Also, it would be helpful if that was said in the readme.
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 with the README and issue #265, then trace the project’s documentation or implementation references relevant to lock-freeness and huge-page allocation. Establish whether the stated guarantees still hold, including deterministic allocation and deallocation timing, and document the supported conclusion in the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- documentation, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100