mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-10 03:41:24 +01:00
45bf1a82f1
qc_may_build_pkt() has been modified several times regardless of the conditions the functions it is supposed to allow to send packets (qc_build_pkt()/qc_do_build_pkt()) really use to finally send packets just after having received others, leading to contraditions and possible very long loops sending empty packets (PADDING only packets) because qc_may_build_pkt() could allow qc_build_pkt()/qc_do_build_pkt to build packet, and the latter did nothing except sending PADDING frames, because from its point of view they had nothing to send. For now on, this is the job of qc_may_build_pkt() to decide to if there is packets to send just after having received others AND to provide this information to the qc_build_pkt()/qc_do_build_pkt() Note that the unique case where the acknowledgements are completely ignored is when the endpoint must probe. But at least this is when sending at most two datagrams! This commit also fixes the issue reported by Willy about a very low throughput performance when the client serialized its requests. Must be backported to 2.7 and 2.6.
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)