Tim Brooks 2dc686ded1 Prefer direct io buffers if direct buffers pooled (#9167) ... Motivation Direct buffers are normally preferred when interfacing with raw sockets. Currently netty will only return direct io buffers (for reading from a channel) when a platform has unsafe. However, this is inconsistent with the write-side (filterOutboundMessage) where a direct byte buffer will be returned if pooling is enabled. This means that environments without unsafe (and no manual netty configurations) end up with many pooled heap byte buffers for reading, many pooled direct byte buffers for writing, and jdk pooled byte buffers (for reading). Modifications This commit modifies the AbstractByteBufAllocator to return a direct byte buffer for io handling when the platform has unsafe or direct byte buffers are pooled. Result: Use direct buffers when direct buffers are pooled for IO.		2019-05-22 07:32:41 +02:00
..
src	Prefer direct io buffers if direct buffers pooled (#9167)	2019-05-22 07:32:41 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2019-04-30 16:42:29 +00:00