Kernel out of memory (OOM)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
One critical issue that the LVBS kernel platform suffers from is OOM. Currently, we are trying to avoid this issue in conservative and ad-hoc manners like restricting the number of active userspace instances/sessions (i.e., processes/threads) and the size of buffers for syscalls and inter-world communications. This approach can waste a large portion of secure-world memory block some normal app behaviors.
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
No file, test, or entry point is identified in the issue. First map how the LVBS kernel accounts for secure-world memory and handles userspace sessions, syscall buffers, and inter-world communication; done requires addressing OOM without relying only on the current ad hoc restrictions and confirming normal application behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100