mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 06:11:32 +02:00
06e66c84fc
Many inline functions involve some BUG_ON() calls and because of the partial complexity of the functions, they're not inlined anymore (e.g. co_data()). The reason is that the expression instantiates the message, its size, sometimes a counter, then the atomic OR to taint the process, and the back trace. That can be a lot for an inline function and most of it is always the same. This commit modifies this by delegating the common parts to a dedicated function "complain()" that takes care of updating the counter if needed, writing the message and measuring its length, and tainting the process. This way the caller only has to check a condition, pass a pointer to the preset message, and the info about the type (bug or warn) for the tainting, then decide whether to dump or crash. Note that this part could also be moved to the function but resulted in complain() always being at the top of the stack, which didn't seem like an improvement. Thanks to these changes, the BUG_ON() calls do not result in uninlining functions anymore and the overall code size was reduced by 60 to 120 kB depending on the build options.
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)