andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
e053b96b5c
netty5/transport-native-epoll
History
Scott Mitchell 5b48fc284e Make OIO/NIO/EPOLL autoReadClear consistent 
Motivation:
OIO/NIO use a volatile variable to track if a read is pending. EPOLL does not use a volatile an executes a Runnable on the event loop thread to set readPending to false. These mechansims should be consistent, and not using a volatile variable is preferable because the variable is written to frequently in the event loop thread.
OIO also does not set readPending to false before each fireChannelRead operation and may result in reading more data than the user desires.

Modifications:
- OIO/NIO should not use a volatile variable for readPending
- OIO should set readPending to false before each fireChannelRead

Result:
OIO/NIO/EPOLL are more consistent w.r.t. readPending and volatile variable operations are reduced
Fixes https://github.com/netty/netty/issues/5069
2016-04-06 12:32:14 -07:00
..
src Make OIO/NIO/EPOLL autoReadClear consistent 2016-04-06 12:32:14 -07:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
README.md Introduce a native transport for linux using epoll ET 2014-02-15 22:44:56 +01:00

README.md

Native transport for Linux

See our wiki page.