oxidecomputer / oxidecomputer/opte
Move stats from TcpFlowEntryState to UftEntry
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
The segs/bytes stats on TcpFlowEntryState should really be in the UftEntry. That way we track these stats for all flows, not just TCP flows.
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
Locate the definitions of TcpFlowEntryState and UftEntry and inspect how the segs/bytes statistics are updated and read. Move the statistics to UftEntry so they are tracked for all flows rather than only TCP flows, then verify the affected flow-stat handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100