oxidecomputer / oxidecomputer/dlpi-sys
Use of tokio asyncfd introduces significant performance regression
Open
Nobody has claimed this yet.
bug
regression
- Dominant language
- Rust
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
After this commit ca2366e communications through dlpi devices have noticeable lag and are much slower than they were.
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 by comparing commit ca2366e with its parent and tracing the tokio asyncfd change that affects communications through dlpi devices. Reproduce the reported lag and compare performance against the pre-commit behavior; done means identifying and correcting the regression with evidence that communication speed is restored.
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
- Needs clarification
- Newbie friendliness
- 25/100