DanielBarton446 / DanielBarton446/reverse_tcp_proxy
Feature: Move to edge trigger based proxy
- Dominant language
- C
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently this is a Level Triggered reverse proxy. This isn't great for us because the kernel is spamming EPOLLIN and EPOLLOUT events instead of us just fully draining the kernel receive or send queues when we have an event for EPOLLIN or EPOLLOUT.
May have to be careful here though with ensuring the queues get fully drained and dont run into weird situations with queues not being fully drained before needing to handle another event into said queue. need to think more on this.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the reverse proxy's EPOLLIN and EPOLLOUT event loop, then read how receive and send queues are handled. Done means the proxy uses edge-triggered events and safely drains both queues without missing follow-up work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100