Kernel out of memory (OOM)

Open
#846 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Domain
operating-systems

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.

Description

discussion target-lvbs

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.

Dominant language
Rust
Stars
2.7k
Forks
144
Avg merge
12h 21m
Merged PRs (30d)
146

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/litebox

All issues in microsoft/litebox

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.