oxidecomputer / oxidecomputer/crucible
Volume: parallel read dispatch
Open
Nobody has claimed this yet.
mvp
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Currently reads go to the read-only parent and affected sub volumes sequentially. It would be better to fire off both in parallel, wait, then perform the required logic.
BlockIO is not an async trait, nor was the Guest previously async - I'm pretty sure that parallel dispatch requires this?
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
Start by tracing the Volume read path and reviewing the BlockIO and Guest traits mentioned in the issue. Determine how the read-only parent and affected sub volumes are dispatched, then verify that both reads can complete before the required follow-up logic runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100