oxidecomputer / oxidecomputer/hubris
Should we allow the kernel scheduler to idle?
Open
Nobody has claimed this yet.
🤔 design
kernel
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
Currently, the kernel panics if it runs out of schedulable tasks, meaning we have to remember to include an idle task in every image. This burns text and RAM -- perhaps we should let the scheduler idle internally?
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 files or tests are named in the issue. Start by tracing the kernel scheduler's panic path and how images currently provide an idle task. Define the scheduler's idle behavior and the resource savings expected before identifying tests that demonstrate the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100