Design fair servicing for sustained VM and host traffic
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 83
- Forks
- 32
- Avg merge
- 7h 44m
- Merged PRs (30d)
- 1
Description
See https://github.com/openai/softnet/pull/196#discussion_r3799008607.
We currently have an exception for service_control(), which runs each 128 packets: https://github.com/openai/softnet/blob/df0874b4db8454e828ab74c7f1736f8a23f9935b/lib/proxy/mod.rs#L160-L163
It would be nice to assess the security and performance implications of either:
- not doing this; or
- doing this for other periodic routines like
port_forwarder.tick()too
And implement a more consistent approach.
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
Read the linked pull request discussion and lib/proxy/mod.rs around service_control(), then inspect how port_forwarder.tick() is serviced. Assess the security and performance implications of the two proposed approaches and define what a consistent servicing policy should cover. Done means implementing the chosen approach and validating its impact on sustained VM and host traffic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, performance, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100