mirror of
https://github.com/haproxy/haproxy.git
synced 2026-04-21 06:06:59 -04:00
HAProxy - Load balancer
db5d1a1b19
For the moment, the transport layer function qc_send_app_pkts lacks features. Most notably, it only send up to a single Tx buffer and won't retry even if there is frames left and its Tx buffer is now empty. To overcome this limitation, the MUX implements an opportunistic retry sending mechanism. qc_send_app_pkts is repeatedly called until the transport layer is blocked on an external condition (such as congestion control or a sendto syscall error). The blocking was detected by inspecting the frame list before and after qc_send_app_pkts. If no frame has been poped by the function, we considered the transport layer to be blocked and we stop to send. The MUX is subscribed on the lower layer to send the frames left. However, in case of STREAM frames, qc_send_app_pkts might use only a portion of the data and update the frame offset. So, for STREAM frames, a new mechanism is implemented : if the offset field of the first frame has not been incremented, it means the transport layer is blocked. This should improve transfers execution. Before this change, there is a possibility of interrupted transfer if the mux has not sent everything possible and is waiting on a transport signaling which will never happen. In the future, qc_send_app_pkts should be extended to retry sending by itself. All this code burden will be removed from the MUX. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
The HAProxy documentation has been split into a number of different files for ease of use. 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)