Consider compiling WSL2 kernel with -O3 for all archs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Provides a performance boost to the kernel.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
A more performant kernel based on compiling optimizations provided by -O3.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
Build the kernel myself with this compilation option.
**Additional context**
Add any other context or screenshots about the feature request here.
See https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.19-O3-March-Native and this patch series: https://lore.kernel.org/lkml/20220621133526.29662-1-mikoxyzzz@gmail.com/ . Found in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/init/Kconfig?h=v5.19
Would suggest backporting this patch to WSL2 kernel to benefit from the performance boost.
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
Start with Linux v5.19's init/Kconfig entry and review the linked patch series and WSL2 kernel build configuration. Check how the proposed -O3 option applies across supported architectures and whether the patch can be backported safely. Done means a validated change that builds successfully for all targeted architectures and demonstrates the intended performance benefit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- build-system, operating-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100