oxidecomputer / oxidecomputer/opte
Clean up ioctl path
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
Ioctls originally went through a DLD specific mechanism but after #321 we'll be handling them directly. As part of that change the general structure wasn't changed to minimize the changes needed. This issue is reevaluate and see if we should handle things differently now that we don't have to stick to the dld ioc semantics. (We may also decide it's ok as-is but nice to have an issue to track 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 reviewing the ioctl changes in #321 and tracing the current ioctl path and its remaining DLD-specific structure. Determine whether the post-#321 design should change or remain as-is; done means reaching and documenting that decision, with any resulting cleanup identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100