mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-19 04:00:46 +00:00
haproxy public development tree
af02c57406
The application of a cpu-map statement with both process and threads is broken (P-Q/1 or 1/P-Q notation). For example, before the fix, when using P-Q/1, proc_t1 would be updated. Then it would be AND'ed with thread which is still 0 and thus does nothing. Another problem is when using 1/1[-Q], thread[0] is defined. But if there is multiple processes, every processes will use this define affinity even if it should be applied only to 1st process. The solution to the fix is a little bit too complex for my taste and there is maybe a simpler solution but I did not wish to break the storage of global.cpu_map, as it is quite painful to test all the use-cases. Besides, this code will probably be clean up when multiprocess support removed on the future version. Let's try to explain my logic. * either haproxy runs in multiprocess or multithread mode. If on multiprocess, we should consider proc_t1 (P-Q/1 notation). If on multithread, we should consider thread (1/P-Q notation). However during parsing, the final number of processes or threads is unknown, thus we have to consider the two possibilities. * there is a special case for the first thread / first process which is present in both execution modes. And as a matter of fact cpu-map 1 or 1/1 notation represents the same thing. Thus, thread[0] and proc_t1[0] represents the same thing. To solve this problem, only thread[0] is used for this special case. This fix must be backported up to 2.0. |
||
---|---|---|
.github | ||
addons | ||
admin | ||
dev | ||
doc | ||
examples | ||
include | ||
reg-tests | ||
scripts | ||
src | ||
tests | ||
.cirrus.yml | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
BRANCHES | ||
CHANGELOG | ||
CONTRIBUTING | ||
INSTALL | ||
LICENSE | ||
MAINTAINERS | ||
Makefile | ||
README | ||
ROADMAP | ||
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)