mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-28 14:21:00 +01:00
91b2305ad7
Each time data is read on QUIC receiver socket, we try to reuse the first datagram of the currently used quic_receiver_buf instead of allocating a new one. This algorithm is suboptimal if there is several unused datagrams as only the first one is tested and its buffer removed from quic_receiver_buf. If QUIC traffic is quite substential, this can lead to an important number of quic_dgram occurences allocated from pool_head_quic_dgram and a lack of free space in allocated quic_receiver_buf buffers. To improve this, each time we want to reuse a datagram, we pop elements until a non-yet released datagram is found or the list is empty. All intermediary elements are freed and the last found datagram can be reused. This operation has been extracted in a dedicated function named quic_rxbuf_purge_dgrams(). This should improve memory consumption incured by quic_dgram instances under heavy QUIC traffic. Note that there is still room for improvement as if the first datagram is still in use, it may block several unused datagram after him. However this requires to support removal of datagrams out of order which is currently not possible. This should be backported up to 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)