mirror of
https://github.com/haproxy/haproxy.git
synced 2026-03-03 13:50:26 -05:00
HAProxy - Load balancer
67c99db0a7
As documented, the NUMA auto-detection is not supposed to be used when the CPU affinity was set either by taskset (already checked) or by a cpu-map directive. However this check was missing, so that configs having cpu-map entries would still first bind to a single node. In practice it has no impact on correct configs since bindings will be replaced. However for those where the cpu-map directive are not exhaustive it will have the impact of binding those threads to one node, which disagrees with the doc (and makes future evolutions significantly more complicated). This could be backported to 2.4 where numa-cpu-mapping was added, though if nobody encountered this by then maybe we should only focus on recent versions that are more NUMA-friendly (e.g. 2.8 only). This patch depends on this previous commit that brings the function we rely on: MINOR: cpuset: add cpu_map_configured() to know if a cpu-map was found |
||
|---|---|---|
| .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)