60f64449fb
Implement support for multiple Rx buffers per QCS instances. This requires several changes mostly in qcc_recv() / qcc_decode_qcs() which deal with STREAM frames reception and decoding. These multiple buffers can be stored in QCS rx.bufs tree which was introduced in an earlier patch. On STREAM frame reception, a buffer is retrieved from QCS bufs tree, or allocated if necessary, based on the data starting offset. Each buffers are aligned on bufsize for convenience. This ensures there is no overlap between two contiguous buffers. Special care is taken when dealing with a STREAM frame which must be splitted and stored in two contiguous buffers. When decoding input data, qcc_decode_qcs() is still invoked with a single buffer as input. This requires a new while loop to ensure decoding is performed accross multiple contiguous buffers until all data are decoded or app stream buffer is full. Also, after qcs_consume() has been performed, the stream Rx channel is immediately closed if FIN was already received and QCS now contains only a single buffer with all remaining data. This is necessary as qcc_recv() is unable to close the Rx channel if FIN is received for a buffer different from the current readable offset. Note that for now stream flow-control value is still too low to fully utilizing this new infrastructure and improve clients upload throughput. Indeed, flow-control max-stream-data initial values are set to match bufsize. This ensures that each QCS will use 1 buffer, or at most 2 if data are splitted. A future patch will increase this value to unblock this limitation.
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
Please refer to the following files depending on what you're looking for:
- INSTALL for instructions on how to build and install HAProxy
- BRANCHES to understand the project's life cycle and what version to use
- LICENSE for the project's license
- CONTRIBUTING for the process to follow to submit contributions
The more detailed documentation is located into the doc/ directory:
- doc/intro.txt for a quick introduction on HAProxy
- doc/configuration.txt for the configuration's reference manual
- doc/lua.txt for the Lua's reference manual
- doc/SPOE.txt for how to use the SPOE engine
- doc/network-namespaces.txt for how to use network namespaces under Linux
- doc/management.txt for the management guide
- doc/regression-testing.txt for how to use the regression testing suite
- doc/peers.txt for the peers protocol reference
- doc/coding-style.txt for how to adopt HAProxy's coding style
- doc/internals for developer-specific documentation (not all up to date)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.