Tracking Task Prioritization
Open
@wdcui is already working on this.
Since Sep 17, 2025.
layer-META
tracking-issue
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
Tracking tasks that @CvvT, @wdcui and I discussed and prioritized this afternoon:
P0 tasks:
- fs + switch stack + ... towards std in user platform support (#341)
- FD cleanup (#31)
- fixing the non-deterministic failures that sometimes show up on CI (e.g.)
- adding more syscall support for benchmarks
- perf measurement and optimization
P1 tasks:
- SNP Platform (single instance)
- SIMD support (https://github.com/microsoft/litebox/issues/64)
P1.5 task:
- Signal Handling (#347)
P2 tasks:
- Wasm shim
- N/W IP -> Eth (#21)
P3 tasks:
- syscall callback (shim <-> platform) cleanup
- shared runner
- nicer multi-instance support (related: #356)
- consider Syscall User Dispatch on Linux platform, as an alternative to systrap backend
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.
Assessment
This issue has not been assessed yet.