Scott Mitchell ce241bd11e Epoll flush/writabilityChange deadlock ... Motivation: b215794de3 recently introduced a change in behavior where writeSpinCount provided a limit for how many write operations were attempted per flush operation. However when the write quantum was meet the selector write flag was not cleared, and the channel unsafe flush0 method has an optimization which prematurely exits if the write flag is set. This may lead to no write progress being made under the following scenario: - flush is called, but the socket can't accept all data, we set the write flag - the selector wakes us up because the socket is writable, we write data and use the writeSpinCount quantum - we then schedule a flush() on the EventLoop to execute later, however it the flush0 optimization prematurely exits because the write flag is still set In this scenario the socket is still writable so the EventLoop may never notify us that the socket is writable, and therefore we may never attempt to flush data to the OS. Modifications: - When the writeSpinCount quantum is exceeded we should clear the selector write flag Result: Fixes https://github.com/netty/netty/issues/7729		2018-02-20 11:40:58 +01:00
..
src/main/java/io/netty/testsuite	Epoll flush/writabilityChange deadlock	2018-02-20 11:40:58 +01:00
.gitignore	updated udt and connection test	2013-05-14 06:46:07 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2018-02-05 12:02:35 +00:00