14710b5e6b
A newly introduced frames list member has been defined into QCC instance with pacing implementation. This allowed to preserve STREAM frames built between different emission scheduled by pacing, without having to regenerate it if no new QCS data is available. Generalize this principle outside of pacing scheduling. Now, the frames list will be reused accross several qcc_io_send() usage. Frames list is only cleared when necessary. This will force its refreshing in the next qcc_io_send() via qcc_build_frms_list(). Frames list refreshing is performed in the following cases : * on successful transfer from stream snd_buf / done_ff / shut * on stream reset or read abort * on max_data/max_stream_data reception with window increase Note that the two first cases are in fact covered directly due to qcc_send_stream() usage when QCS is (re)inserted into the send_list. The main objective of this patch will be to remove QUIC MUX pacing specific code path. It could also provide better performance as emission of large frames may often be rescheduled due to transport layer, either on congestion or full socket buffer. When QUIC MUX is rescheduled, no new data is available and frames list can be reuse as-is, avoiding an unecessary loop over send_list. This should be backported up to 3.1. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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.