mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 22:01:31 +02:00
92c059c2ac
The current BTS/BTR operations on x86 are ugly because they rely on a CAS, so they may be unfair and take time to converge. Fortunately, where they are currently used (mostly FDs) the contention is expected to be rare (mostly listeners). But this also limits their use to such few low-load cases. On x86 there is a set of BTS/BTR instructions which help for this, but before the FD's state migrated to 32 bits there was little use of them since they do not exist in 8 bits. Now at least it makes sense to use them, at the very least in order to significantly reduce the code size (one BTS instead of a CMPXCHG loop). The implementation relies on modern gcc's ability to return condition flags and limit code inflation and register spilling. The fall back is retained on the old implementation for all other situations (inappropriate target size or non-capable compiler). The code shrank by 1.6 kB on the fast path. As expected, for now on up to 4 threads there is no measurable difference of performance.
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)