Epoll: Remove edge-triggered support #14007
Assignees
Milestone
Comments
normanmaurer
added a commit
that referenced
this issue
May 3, 2024
…ggered Motivation: We supported edge-triggered and level-triggered modes for our epoll transport. This made things more complex while not really providing much value. Modifications: - Remove edge-triggered support and just use level-triggered all the time Result: Less complexity. Fixes #14007
normanmaurer
added a commit
that referenced
this issue
May 3, 2024
#14031) …ggered Motivation: We supported edge-triggered and level-triggered modes for our epoll transport. This made things more complex while not really providing much value. Modifications: - Remove edge-triggered support and just use level-triggered all the time Result: Less complexity. Fixes #14007
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Back in the days when we wrote the native epoll transport we decided to use edge triggered by default but also support level triggered. Supporting edge-triggered complicates things a lot while the advantage is not really clear with the dispatching model of netty. Let's remove edge-triggered and just use level-triggered.
The text was updated successfully, but these errors were encountered: