oxidecomputer / oxidecomputer/propolis
SoftNpu should halt worker threads on `Entity::halt`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
SoftNpu runs a worker thread per ASIC port that acts as a DLPI receiver for that port. When the VM instance is halted, these threads should also be halted, as there is nowhere for them to send packets, and they could prevent the instance process from exiting cleanly.
Contributor guide
No contributing guide indexed for this repository
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 at SoftNpu's per-ASIC-port worker setup and the Entity::halt path; trace how the DLPI receiver threads are owned and how lifecycle shutdown is coordinated. Done means halting the VM also stops these workers, allowing the instance process to exit cleanly; verify with the relevant existing tests or a focused halt-and-exit run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100