oxidecomputer / oxidecomputer/propolis
nvme: would be nice to test I/O!
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
I'm imminently going to merge https://github.com/oxidecomputer/propolis/pull/966, and when that's in ... the driver-ish morass in FuzzCtz has the same issue as I outlined in https://github.com/oxidecomputer/propolis/issues/1174: it sets up an NVMe controller and sets up some queues and stuff, but doesn't actually do disk I/O. which means there's no I/O during the random migrations, no I/O during controller resets, a whole bunch of interesting state space is missed.
I think the same idea as #1174 applies here: we can just be a poll-mode driver watching completion queue heads and doing whatever needs doing with completions as stuff changes. bonus: we can spin on doorbell buffer heads and make sure those are reasonable!
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 with the driver-like setup in FuzzCtz and compare the approach described in issue #1174, after reviewing the context from pull request #966. The work is done when the NVMe fuzzing path performs disk I/O during random migrations and controller resets, processes completion queue changes, and checks doorbell buffer heads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100