Go to file
Norman Maurer db74b2344f Not try to allocate out of the PoolChunkList that contains only full PoolChunks
Motivation:

When doing a normal allocation in PoolArena we also tried to allocate out of the PoolChunkList that only contains completely full PoolChunks. This makes no sense as these are full anyway so an allocation will never work here and just gives a perf hit as we need to walk the whole list of PoolChunks in the list.

Modifications:

Not try to allocate from PoolChunkList that only contains full PoolChunks

Result:

Faster allocation times when a new PoolChunk must be created.
2016-04-09 18:39:33 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
buffer Not try to allocate out of the PoolChunkList that contains only full PoolChunks 2016-04-09 18:39:33 +02:00
codec [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
codec-http [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
common Make all InternalLoggerFactory implementations be singletons 2016-04-08 09:39:47 +02:00
example [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
handler fcbeebf6df unit test bug 2016-04-06 00:12:54 -07:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
transport [#5028] Fix re-entrance issue with channelWritabilityChanged(...) and write(...) 2016-04-06 10:50:41 +02:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-04-04 16:53:40 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Add Log4J2LoggerFactory and Log4J2Logger 2016-04-05 14:07:26 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

Branches to look

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.