mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-08-06 07:07:04 +02:00
ddd8671b19
When user specifies a maxlen parameter that is greater than the size of a given ring section, a warning is emitted to inform that the max length exceeds size, and then the maxlen is forced to size. The logic is good, but imprecise, because it doesn't take into account the slight overhead from storing payloads into the ring. In practise, we cannot store a single message which is exactly the same length than size. Doing so will result in the message being dropped at runtime. Thanks to the ring_max_payload() function introduced in "MINOR: ring: add a function to compute max ring payload", we can now deduce the maximum value for the maxlen parameter before it could result in messages being dropped. When maxlen value is set to an improper value, the warning will be emitted and maxlen will be forced to the maximum "single" payload len that could fit in the ring buffer, preventing messages from being dropped unexpectedly. This commit depends on: - "MINOR: ring: add a function to compute max ring payload" This may be backported as far as 2.2 |
||
|---|---|---|
| .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 | ||
| 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)