microsoft / microsoft/mimalloc
mimalloc with MIMALLOC_RESERVE_HUGE_OS_PAGES=2 falls back to 4KB pages after exhausting 1GB pages without warning.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
I am using mimalloc in an application where I reserve 2 1GB huge pages. After a while when the application has exhausted this limit mimalloc falls back to 4KB pages (analysed /proc//smaps). I wanted to know if I could enable some flag to produce a warning when this change to 4KB page happens.
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 MIMALLOC_RESERVE_HUGE_OS_PAGES=2 configuration and reproduce exhaustion of the reserved 1GB huge pages, checking /proc//smaps for the fallback to 4KB pages. Trace the huge-page allocation and fallback entry points, then determine how a warning should be exposed; done means the transition produces a warning without changing the fallback behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100