Allow pre-allocation of HugePages for WSL2
Open
Nobody has claimed this yet.
feature
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
For traditional Hyper-V VMs, it is possible to enable HugePages allocation for a VM using Set-VMMemory -HugePagesEnabled, but it is not possible to do so for WSL2. Considering that WSL2 memory is dynamically allocated, to avoid fragmentation, it is best to allow users to specify a fixed size of HugePages that will be allocated and never freed at WSL2 startup.
Contributor guide
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
The issue names no files, tests, or implementation entry points. Start by locating WSL2 startup memory allocation and the HugePages behavior associated with Set-VMMemory; done means users can specify a fixed HugePages size for WSL2 and that allocation is retained after startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100